OpenshiftApplication · Redhat
CVE-2015-7537
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 · uneditedCross-site request forgery (CSRF) vulnerability in Jenkins before 1.640 and LTS before 1.625.2 allows remote attackers to hijack the authentication of administrators for requests that have unspecified impact via vectors related to the HTTP GET method.
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 confidenceCSRF vulnerability in Jenkins versions before 1.640 and LTS before 1.625.2 allows remote attackers to hijack administrator authentication sessions by tricking admin users into making HTTP GET requests to malicious URLs, potentially enabling unauthorized administrative actions on the Jenkins server.
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.639CVSS 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
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Determine Jenkins version via HTTP APISend a GET request to the Jenkins server root endpoint (e.g., http://yourjenkins/api/json or /api/xml) and locate the 'version' field in the JSON response. Alternatively, access Manage Jenkins > About Jenkins to view the version number displayed on the UI.Affected if The displayed version is 1.639 or earlier, or any version before LTS 1.625.2 (such as 1.625.1, 1.625, 1.624, etc.)
-
Identify if running Red Hat OpenShift with embedded JenkinsIf the Jenkins instance is embedded within Red Hat OpenShift, check the OpenShift version by running 'oc version' or accessing the OpenShift web console. The embedded Jenkins version typically matches the OpenShift version.Affected if Running OpenShift version 2.0 or any version 3.1 and earlier that includes an embedded Jenkins instance falling within the affected version range.
-
Verify CSRF protection (crumb) configuration statusNavigate to Manage Jenkins > Configure Global Security. Under the 'CSRF Protection' section, confirm whether the 'Enable proxy compatibility' or default crumb implementation is enabled. Alternatively, query the API: send a GET request to /api/json?tree=useCrumbs,crumbRequestField and check the 'useCrumbs' value.Affected if CSRF protection is disabled (useCrumbs returns false) or no crumb is required for requests, allowing unauthenticated or tricked admin actions.
You are affected if your Jenkins version is 1.639 or earlier (or any version before LTS 1.625.2, or embedded in OpenShift 2.0/3.1 and below) AND the CSRF protection (crumb) is disabled or misconfigured.
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.640 or later (or LTS 1.625.2 or later). Additionally, ensure the built-in CSRF protection (crumb default) remains enabled and verify no custom configurations disable it.
Fix this in Openshift
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-7537 — 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-7537 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