OpenshiftApplication · Redhat
CVE-2015-5323
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedJenkins 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceJenkins before 1.638 and LTS before 1.625.2 do not properly restrict access to API tokens, which could allow an authenticated remote administrator to use the API token of another user to gain elevated privileges and execute scripts.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
OpenshiftApplication
<= 3.1= 2.0
JenkinsApplication
<= 1.625.1<= 1.637CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify your Jenkins installation type and versionCheck the Jenkins version by visiting /api/json on the Jenkins server or checking the server console output at startup. For weekly releases, note the exact version number. For LTS, identify it as LTS and note the version (e.g., 1.625.1, 1.625.2).Affected if The installed version is Jenkins <= 1.637 (weekly) or Jenkins LTS <= 1.625.1 (LTS).
-
Determine if running on Red Hat OpenShiftCheck if your Jenkins instance is deployed on Red Hat OpenShift. Verify the OpenShift version by running 'oc version' or checking the project configuration.Affected if Running Jenkins on OpenShift version 2.0 or <= 3.1.
-
Confirm API token functionality is enabledAPI tokens are generated per user. Check if any users have API tokens configured by accessing the user configuration page (e.g., /user/[username]/configure) or by querying the API: /api/json?tree=users[apiToken].Affected if API tokens exist for any user account in the Jenkins instance.
-
Verify remote API access is permittedTest if the Jenkins remote API is accessible by making an authenticated request to the /api/json endpoint using administrator credentials.Affected if Remote API access is enabled and administrators can make authenticated API calls.
A user is affected if they run Jenkins weekly <= 1.637 or LTS <= 1.625.1 (or on OpenShift 2.0 or <= 3.1) AND have API tokens configured for users, allowing an authenticated admin to access another user's token.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Jenkins to version 1.638 (weekly) or 1.625.2 (LTS) or later to properly restrict API token access and prevent unauthorized token usage.
Fix this in Openshift
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5323 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-5323 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data