JenkinsApplication
CVE-2015-1814
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 · uneditedThe API token-issuing service in Jenkins before 1.606 and LTS before 1.596.2 allows remote attackers to gain privileges via a "forced API token change" involving anonymous users.
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 versions before 1.606 (weekly) and 1.596.2 (LTS) contain a vulnerability in the API token-issuing service where a forced API token change mechanism can be exploited by remote attackers to gain elevated privileges, specifically targeting anonymous users.
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
JenkinsApplication
= 1.596.1<= 1.605
OpenshiftApplication
<= 3.1CVSS 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
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/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 Jenkins versionAccess the Jenkins web interface and locate the version number in the page footer, or query the /api/json endpoint for the 'version' fieldAffected if version is 1.596.1 or 1.596 (LTS) or any version from 1.596.2 up to 1.605 (weekly)
-
Confirm Jenkins release lineDetermine whether the installed version is a weekly release or an LTS release by checking the version number format and Jenkins release historyAffected if running a weekly release <= 1.605 or an LTS release <= 1.596.1
-
Verify anonymous access is enabledNavigate to 'Manage Jenkins' > 'Configure Global Security' and check if 'Enable anonymous access' or similar option is checked under Security Realm or Authorization settingsAffected if anonymous users have read or greater access privileges
-
Check API token configurationNavigate to a user's configuration page (typically /user/[username]/configure) and examine the API Token section to see if tokens exist or if forced token regeneration is possible via the UI or APIAffected if API tokens are present and anonymous access is enabled
Environment is affected if running Jenkins version 1.596.1 or 1.596 (LTS), or any weekly version between 1.597 and 1.605, with anonymous access granted to the system.
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.606 or later (weekly) or 1.596.2 or later (LTS). Until upgraded, disable anonymous access or implement additional network-level access controls.
Fix this in Jenkins
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1814 — 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-1814 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