Build Failure AnalyzerApplication · Jenkins
CVE-2019-16553
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 · uneditedA cross-site request forgery vulnerability in Jenkins Build Failure Analyzer Plugin 1.24.1 and earlier allows attackers to have Jenkins evaluate a computationally expensive regular expression.
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 confidenceA CSRF vulnerability in Jenkins Build Failure Analyzer Plugin versions 1.24.1 and earlier allows authenticated users to be tricked into submitting requests that trigger evaluation of computationally expensive regular expressions, causing potential denial of service through resource exhaustion.
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
Build Failure AnalyzerApplication
<= 1.24.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
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/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.
-
Check if Build Failure Analyzer plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Build Failure Analyzer' or check the plugin directory $JENKINS_HOME/plugins for build-failure-analyzer directoryAffected if Plugin is not found in the installed plugins list or directory
-
Determine the installed version of Build Failure AnalyzerIn Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed tab, find Build Failure Analyzer and note the version column; alternatively, inspect the $JENKINS_HOME/plugins/build-failure-analyzer/META-INF/MANIFEST.MF file for the Plugin-Version attributeAffected if Version is 1.24.1 or earlier (any version <= 1.24.1)
-
Check global Jenkins CSRF protection statusNavigate to Manage Jenkins > Configure Global Security > CSRF Protection section; verify if 'Enable Crumb' or 'CSRF Protection' is checked/enabledAffected if Global CSRF protection is disabled (unchecked), making the environment vulnerable to the CSRF attack vector
The environment is affected if Build Failure Analyzer plugin version is 1.24.1 or earlier AND global Jenkins CSRF protection is disabled (if CSRF protection is enabled, the attack vector is mitigated).
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 Build Failure Analyzer Plugin version 1.24.2 or later which includes CSRF protection; alternatively ensure global Jenkins CSRF protection (crumb) is enabled.
Fix this in Build Failure Analyzer
Scoped from the published advisory
- Consultation2.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-16553 — 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-16553 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