OpenshiftApplication · Redhat
CVE-2015-5321
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 sidepanel widgets in the CLI command overview and help pages in Jenkins before 1.638 and LTS before 1.625.2 allow remote attackers to obtain sensitive information via a direct request to the pages.
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 confidenceThe sidepanel widgets in Jenkins CLI command overview and help pages before versions 1.638 and LTS 1.625.2 expose sensitive information to remote attackers via direct requests to these pages. This is an information disclosure vulnerability where unauthenticated users can access the sidepanel content that should be restricted.
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
- 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.
-
Identify the Jenkins versionNavigate to Manage Jenkins > About Jenkins or check the jenkins.war file version. On Linux, run: java -jar jenkins.war --versionAffected if The installed version is 1.637 or earlier, or LTS 1.625.1 or earlier
-
Verify if anonymous read access is enabledNavigate to Manage Jenkins > Configure Global Security. Under Authorization, check if 'Anyone can do anything' or 'Anonymous read access' is selected.Affected if Anonymous users have any level of read or full access to Jenkins
-
Test access to CLI help pages without authenticationOpen a browser in incognito mode and navigate to: http://your-jenkins-host:8080/cli/help. Also try accessing the sidepanel directly via any /cli/ URLs while logged out.Affected if The pages load and display content without requiring login credentials
-
Check for sensitive information in CLI overviewAccess the CLI command overview page (typically at /cli/) as an anonymous user and inspect whether job names, build histories, or configuration details are visible in the sidepanel widgets.Affected if Unauthenticated users can view sidepanel content containing job names, build logs, or other sensitive data
A defender is affected if running Jenkins version 1.637 or earlier (or LTS 1.625.1 or earlier) AND anonymous users can access the CLI help or overview pages and view sidepanel content that should require 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 remediate this vulnerability.
Fix this in Openshift
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5321 — 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-5321 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