GHSA-543w-gq76-pw7g — build-failure-analyzer
HIGHFix: jenkinsci/build-failure-analyzer-plugin@f316c88GHSA-543w-gq76-pw7g is a high-severity (CVSS 8.8) vulnerability in com.sonyericsson.jenkins.plugins.bfa:build-failure-analyzer. A fix is available for com.sonyericsson.jenkins.plugins.bfa:build-failure-analyzer — see the affected versions and patch details below.
Cross-Site Request Forgery in Jenkins Build Failure Analyzer Plugin
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-543w-gq76-pw7g plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
com.sonyericsson.jenkins.plugins.bfa:build-failure-analyzerReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
A 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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.sonyericsson.jenkins.plugins.bfa:build-failure-analyzer | all versions | 1.24.2com.sonyericsson.jenkins.plugins.bfa:build-failure-analyzer:1.24.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.sonyericsson.jenkins.plugins.bfa:build-failure-analyzer, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.sonyericsson.jenkins.plugins.bfa:build-failure-analyzer to 1.24.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-543w-gq76-pw7g is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-543w-gq76-pw7g can be triaged on real exposure rather than presence alone.
Tailored to GHSA-543w-gq76-pw7g. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-543w-gq76-pw7g in your dependencies?
O3 Security finds GHSA-543w-gq76-pw7g across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.