JenkinsApplication
CVE-2015-5324
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 allow remote attackers to obtain sensitive information via a direct request to queue/api.
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 · moderate confidenceThis is an information disclosure vulnerability in Jenkins where the /queue/api endpoint is accessible without proper authentication, allowing remote attackers to obtain sensitive information about build queue contents including job names, build parameters, and potentially user credentials that may be visible in queue entries.
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.625.1<= 1.637
OpenshiftApplication
= 2.0<= 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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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.
-
Check Jenkins versionNavigate to Jenkins > Manage Jenkins > About Jenkins or check the version from the login page or WAR file. On Linux, also check: rpm -q jenkins or dpkg -l jenkinsAffected if The installed version is 1.625.1 or earlier, or 1.637 or earlier (for weekly releases), indicating the server is within the affected version range.
-
Verify /queue/api accessibilityFrom an unauthenticated browser or using curl -s http://TARGET:8080/queue/api/json (or port 8080 depending on setup). If the endpoint returns JSON data without HTTP 401/403, it is exposed.Affected if The /queue/api endpoint returns queue data (JSON response with 'items' array) without requiring authentication, confirming the vulnerability is present.
-
Confirm authentication is not enforced on API endpointsGo to Jenkins > Manage Jenkins > Configure Global Security. Verify that 'Enable security' is checked and that 'Jenkins' own user database' or an authentication realm is selected under Security Realm, with at least 'Authenticated' permission required under Authorization.Affected if Security is disabled or the /queue/api endpoint allows anonymous read access without requiring authentication, meaning the environment is vulnerable.
The environment is affected if the installed Jenkins version is 1.625.1 or earlier (LTS) or 1.637 or earlier (weekly), and the /queue/api endpoint returns queue data without requiring authentication.
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 or later (or LTS 1.625.2 or later) to patch this vulnerability. Ensure authentication is required for all API endpoints.
Fix this in Jenkins
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-5324 — 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-5324 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