JenkinsApplication
CVE-2019-10353
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 · uneditedCSRF tokens in Jenkins 2.185 and earlier, LTS 2.176.1 and earlier did not expire, thereby allowing attackers able to obtain them to bypass CSRF protection.
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 confidenceIn Jenkins 2.185 and earlier, and LTS 2.176.1 and earlier, CSRF protection tokens (crumb) did not have an expiration time. This means tokens remained valid indefinitely once issued, allowing attackers who obtained a valid token (e.g., through phishing, man-in-the-middle, or log exposure) to perform CSRF attacks at any time in the future.
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
<= 2.176.1<= 2.185CVSS 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/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.
-
Identify installed Jenkins versionNavigate to 'Manage Jenkins' > 'About Jenkins' or access /api/json?tree=mode,nodeDescription,nodeName,numExecutors from the Jenkins server to retrieve the version numberAffected if The version is 2.176.1 or lower for LTS, or 2.185 or lower for weekly releases
-
Verify CSRF protection is not explicitly disabledCheck the Jenkins configuration file (jenkins.model.JenkinsCrumbIssuer or similar in configuration.xml) or go to 'Manage Jenkins' > 'Configure Global Security' and ensure 'Prevent Cross Site Request Forgery exploits' is checkedAffected if CSRF protection is disabled or the crumb issuer setting is missing (vulnerable configuration)
-
Check for crumb issuer configurationLook in $JENKINS_HOME/config.xml for the <crumbIssuer> element, or query the API endpoint /api/json?tree=useCrumbs to see if crumb usage is enabledAffected if The crumbIssuer element exists but contains no expiration-related settings (indicates pre-fix behavior)
-
Review authentication log for token reuseExamine Jenkins access logs (var/log/jenkins/jenkins.log or var/log/jenkins/access_log) for suspicious API calls using older timestamps or patterns indicating replay of old tokensAffected if Multiple API calls using the same crumb value are observed across widely spaced timestamps
A user is affected if their Jenkins version is 2.176.1 or lower (LTS) or 2.185 or lower (weekly), regardless of CSRF protection being enabled, since tokens issued by these versions never expire.
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 to Jenkins 2.186 or LTS 2.176.2 or later, which implements CSRF token expiration. If immediate upgrade is not possible, monitor for unauthorized API usage and consider network segmentation to reduce token exposure risk.
Fix this in Jenkins
Scoped from the published advisory
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10353 — 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-2019-10353 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