Build Failure AnalyzerApplication · Jenkins
CVE-2019-16555
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 user-supplied regular expression in Jenkins Build Failure Analyzer Plugin 1.24.1 and earlier was processed in a way that wasn't interruptible, allowing attackers to have Jenkins evaluate a regular expression without the ability to interrupt this process.
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 confidenceThe Build Failure Analyzer Plugin processes user-supplied regular expressions without timeout or interrupt capability. An attacker who can configure build failure analyzer rules (or possibly trigger builds with specially crafted content analyzed by the plugin) can cause Jenkins to evaluate a regex that runs indefinitely, leading to 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.
-
Locate Build Failure Analyzer plugin versionNavigate to Manage Jenkins > Manage Plugins > Installed tab, or inspect the plugin's .jpi file in $JENKINS_HOME/plugins/ directory. The version is typically listed in the plugin metadata.Affected if The installed version is 1.24.1 or earlier.
-
Identify configured build failure rulesNavigate to Manage Jenkins > Configure Build Failure Analyzer, or inspect the configuration file (typically in $JENKINS_HOME/org.jenkinsci.plugins.buildfailureanalyzer.*.xml). Look for any configured rules that use regex matching patterns.Affected if Any regex-based rules are configured. The vulnerability is triggered when the plugin evaluates a user-supplied regex.
-
Check permission configuration for rule managementReview Jenkins role-based access control (RBAC) or matrix authorization settings. Determine which users or groups have the 'BuildFailureAnalyzer configure' permission or can otherwise modify Build Failure Analyzer rules.Affected if Non-administrator users or unauthenticated attackers can configure rules or trigger builds with content analyzed by the plugin.
-
Review build logs for regex evaluation patternsExamine Jenkins build logs for entries related to Build Failure Analyzer pattern matching, particularly logs showing regex processing or any indication of long-running pattern evaluations.Affected if Build logs show unusually long regex evaluation times or timeout warnings associated with Build Failure Analyzer.
Your environment is affected if the Build Failure Analyzer plugin version is 1.24.1 or earlier AND there are regex-based rules configured, with potential for unauthenticated or non-admin users to trigger malicious regex evaluation.
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 Build Failure Analyzer Plugin to version 1.25.0 or later. If immediate upgrade is not possible, restrict configuration permissions for the plugin to trusted administrators only.
Fix this in Build Failure Analyzer
Scoped from the published advisory
- Consultation2.0 h
- Implementation8.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-16555 — 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-16555 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