Skip to content

GHSA-x4m5-j4x4-4wjg CVE-2015-5323

Jenkins allows Administrators to Access API Tokens

Medium Maven
Severity
0.0 / 10
Medium · CVSS 4.0
Exploit chance (EPSS)
1.49%
Chance of exploitation in the next 30 days. Higher than 74.12% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-522 Insufficiently Protected Credentials
Fix
1.625.2
Upgrade org.jenkins-ci.main:jenkins-core to this version or later

Description

Jenkins before 1.638 and LTS before 1.625.2 do not properly restrict access to API tokens which might allow remote administrators to gain privileges and run scripts by using an API token of another user.

Affected versions

Maven

PackageVulnerableFixed in
org.jenkins-ci.main:jenkins-core
< 1.625.2
1.625.2
org.jenkins-ci.main:jenkins-core
>= 1.626, < 1.638
1.638

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

org.jenkins-ci.main:jenkins-core Maven → 1.625.2

maven
<dependency><groupId>org.jenkins-ci.main</groupId><artifactId>jenkins-core</artifactId><version>1.625.2</version></dependency>
gradle
implementation("org.jenkins-ci.main:jenkins-core:1.625.2")

Severity breakdown

CVSS 4.0 0.0

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

Attack vector
Network
Attack complexity
Low
Attack requirements
None
Privileges required
Low
User interaction
None
Confidentiality (vulnerable system)
Low
Integrity (vulnerable system)
Low
Availability (vulnerable system)
Low
Confidentiality (subsequent systems)
None
Integrity (subsequent systems)
None
Availability (subsequent systems)
None

Weakness

CWE-522: Insufficiently Protected Credentials

The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.

How to prevent it
  • Architecture and Design: Use an appropriate security mechanism to protect the credentials.
  • Architecture and Design: Make appropriate use of cryptography to protect the credentials.
  • Implementation: Use industry standards to protect the credentials (e.g. LDAP, keystore, etc.).

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-6f9g-cxwr-q5jr
Arbitrary file read vulnerability through the Jenkins CLI can lead to RCE
Critical Known exploited Also affects org.jenkins-ci.main:jenkins-core
GHSA-8pqx-3rxx-f5pm
Jenkins discloses project names via fingerprints
High Known exploited Also affects org.jenkins-ci.main:jenkins-core
GHSA-26wc-3wqp-g3rp
Deserialization of Untrusted Data in Jenkins
Critical Known exploited Also affects org.jenkins-ci.main:jenkins-core
CVE-2018-1000861
Deserialization of Untrusted Data in Jenkins
Critical Known exploited Also affects org.jenkins-ci.main:jenkins-core
GHSA-m6wv-wh8g-64xc
Jenkins does not encrypt secrets from POST config.xml submissions before storing them in job configurations
Medium Also affects org.jenkins-ci.main:jenkins-core
GHSA-93qh-vwrm-c5pw
Jenkins: Stored XSS vulnerability in node offline cause description
Medium Also affects org.jenkins-ci.main:jenkins-core
GHSA-92m7-4fpw-2wxm
Jenkins: Open Redirect phishing attacks possible via "from" parameter in "Delegate to servlet container"
Medium Also affects org.jenkins-ci.main:jenkins-core
GHSA-g28p-6mcc-v4rv
Jenkins exposes other users' timezone and view names to users with Overall/Read permission
Medium Also affects org.jenkins-ci.main:jenkins-core
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor