How many CVEs have patched changeApiToken?

1 published CVEs changed changeApiToken in jenkinsci/jenkins, in 1 distinct patches totalling 1 changed lines, between 2015 and 2015.

What is the latest CVE that changed changeApiToken?

CVE-2015-1814 (Jenkins allows for Privilege Escalation by Remote Authenticated Users), published 2015-10-16, changed lines 84 of core/src/main/java/jenkins/security/ApiTokenProperty.java.

How does changeApiToken compare to the rest of jenkinsci/jenkins?

jenkinsci/jenkins has 167 CVEs with a located fix in total; 1 of them changed changeApiToken.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

jenkinsci/jenkins

Function

changeApiToken

Name: changeApiToken in jenkinsci/jenkins: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

core/src/main/java/jenkins/security/ApiTokenProperty.java

Last patched October 16, 2015

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

1

Lines changed

Added plus removed

2015

Years

By CVE publication date

Overview

changeApiToken in jenkinsci/jenkins was changed by 1 published CVE fixes in 2015, in 1 distinct patches that added or removed 1 lines in total.

jenkinsci/jenkins has 167 CVEs with a located fix in total, so 1% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed changeApiToken, newest first, with the lines each fix touched.

Jenkins allows for Privilege Escalation by Remote Authenticated Users
CVE-2015-1814 · line 84 · +1 −0
Medium · CVSS 6.9
EPSS 2.3%2015-10-16

Get an alert when the next CVE fix lands in jenkinsci/jenkins, with the patched functions.

Monitor jenkins CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in jenkinsci/jenkins changed by the most CVE fixes.

serveFile6 CVEs · core/src/main/java/hudson/model/DirectoryBrowserSupport.java Jenkins5 CVEs · core/src/main/java/jenkins/model/Jenkins.java doDynamic4 CVEs · core/src/main/java/hudson/Plugin.java init4 CVEs · core/src/main/java/hudson/util/XStream2.java toString3 CVEs · core/src/main/java/hudson/slaves/OfflineCause.java doSubmitDescription3 CVEs · core/src/main/java/hudson/model/User.java

All patched functions in jenkinsci/jenkins

Frequently asked questions

Common questions about CVE fixes to changeApiToken.

How many CVEs have patched changeApiToken?: 1 published CVEs changed changeApiToken in jenkinsci/jenkins, in 1 distinct patches totalling 1 changed lines, between 2015 and 2015.
What is the latest CVE that changed changeApiToken?: CVE-2015-1814 (Jenkins allows for Privilege Escalation by Remote Authenticated Users), published 2015-10-16, changed lines 84 of core/src/main/java/jenkins/security/ApiTokenProperty.java.
How does changeApiToken compare to the rest of jenkinsci/jenkins?: jenkinsci/jenkins has 167 CVEs with a located fix in total; 1 of them changed changeApiToken.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track jenkinsci/jenkins CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing