How many CVEs have patched ApiTokenProperty_ChangeToken_Success?

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

What is the latest CVE that changed ApiTokenProperty_ChangeToken_Success?

CVE-2015-5323 (Jenkins allows Administrators to Access API Tokens), published 2015-11-25, changed lines 187 to 189 of core/src/main/java/jenkins/security/ApiTokenProperty.java.

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

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

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

Security data

Weaknesses (CWE)The MITRE CWE weakness catalog
Attack Patterns (CAPEC)MITRE CAPEC attack patterns
CNAsNumbering authorities and report cards
VendorsVulnerabilities by vendor
Patched FunctionsWhere CVE fixes land in code

Tools

CVSS CalculatorScore CVSS 4.0, 3.1, 3.0 & 2.0
Badge BuilderEmbeddable SVG badges for READMEs

Resources

LearnSecurity guides
Data SourcesCVE data sources

About Blog Pricing Demo

Home
Patched Functions
Jenkinsci
Jenkins
ApiTokenProperty_ChangeToken_Success

RadicalNotion.AI

We do not sell or share your personal information.

Security Data

CWE Directory
CAPEC Directory
CNA Directory
CNA Leaderboard
CNA Report Cards
Vendor Directory
Patched Functions
Data Sources

Calculators

CVSS Calculator
CVSS 4.0
CVSS 3.1
CVSS 3.0
CVSS 2.0
Badge Builder

Platform

My Vulnerabilities
Insights
Notifications
Pricing

Learn

Guides
What is a CVE?
What is CVSS?
The CISA KEV catalog
What is EPSS?

Company

About
Blog
Careers
Contact
Demo

Account

Legal

Security
Privacy
Terms

RadicalNotion.AI

Security data

Weaknesses (CWE)The MITRE CWE weakness catalog
Attack Patterns (CAPEC)MITRE CAPEC attack patterns
CNAsNumbering authorities and report cards
VendorsVulnerabilities by vendor
Patched FunctionsWhere CVE fixes land in code

Tools

CVSS CalculatorScore CVSS 4.0, 3.1, 3.0 & 2.0
Badge BuilderEmbeddable SVG badges for READMEs

Resources

LearnSecurity guides
Data SourcesCVE data sources

About Blog Pricing Demo

Home
Patched Functions
Jenkinsci
Jenkins
ApiTokenProperty_ChangeToken_Success

ApiTokenProperty_ChangeToken_Success in jenkinsci/jenkins: Patched by 1 CVEs

jenkinsci/jenkins

Function

ApiTokenProperty_ChangeToken_Success

Name: ApiTokenProperty_ChangeToken_Success 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 November 25, 2015

CVEs

That changed this function

Distinct patches

Backports counted once

Lines changed

Added plus removed

2015

Years

By CVE publication date

Overview

ApiTokenProperty_ChangeToken_Success in jenkinsci/jenkins was changed by 1 published CVE fixes in 2015, in 1 distinct patches that added or removed 4 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 ApiTokenProperty_ChangeToken_Success, newest first, with the lines each fix touched.

Jenkins allows Administrators to Access API Tokens
CVE-2015-5323 · lines 187–189 · +3 −1
Medium · CVSS 5.3
EPSS 1.5%2015-11-25

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.

1ApiTokenPropertycore/src/main/java/jenkins/security/ApiTokenProperty.java1 CVEs · 1 patches2013
2changeApiTokencore/src/main/java/jenkins/security/ApiTokenProperty.java1 CVEs · 1 patches2015
3getDisplayNamecore/src/main/java/jenkins/security/ApiTokenProperty.java1 CVEs · 1 patches2013
4hasPermissionToSeeTokencore/src/main/java/jenkins/security/ApiTokenProperty.java1 CVEs · 1 patches2015
5performscore/src/main/java/jenkins/security/ApiTokenProperty.java1 CVEs · 1 patches2015
6setUsercore/src/main/java/jenkins/security/ApiTokenProperty.java1 CVEs · 1 patches2018

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 ApiTokenProperty_ChangeToken_Success.

How many CVEs have patched ApiTokenProperty_ChangeToken_Success?: 1 published CVEs changed ApiTokenProperty_ChangeToken_Success in jenkinsci/jenkins, in 1 distinct patches totalling 4 changed lines, between 2015 and 2015.
What is the latest CVE that changed ApiTokenProperty_ChangeToken_Success?: CVE-2015-5323 (Jenkins allows Administrators to Access API Tokens), published 2015-11-25, changed lines 187 to 189 of core/src/main/java/jenkins/security/ApiTokenProperty.java.
How does ApiTokenProperty_ChangeToken_Success compare to the rest of jenkinsci/jenkins?: jenkinsci/jenkins has 167 CVEs with a located fix in total; 1 of them changed ApiTokenProperty_ChangeToken_Success.
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

core/src/main/java/jenkins/security/ApiTokenProperty.java on GitHub (opens in a new tab)
All patched functions in jenkinsci/jenkins
Patched functions directory

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

On this page

Overview
CVEs that patched it
Other functions in these files
Other hotspots in the repository
FAQ
References