BrakemanApplication · Jenkins
CVE-2020-2122
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 · uneditedJenkins Brakeman Plugin 0.12 and earlier did not escape values received from parsed JSON files when rendering them, resulting in a stored cross-site scripting vulnerability exploitable by users able to control the Brakeman post-build step input data.
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 confidenceThe Jenkins Brakeman Plugin versions 0.12 and earlier contains a stored cross-site scripting (XSS) vulnerability. The plugin parses JSON files from Brakeman scan results but fails to escape output when rendering those values in the UI. An attacker who can control the input data to the Brakeman post-build step (the JSON file content) can inject malicious JavaScript that executes in the browsers of users viewing the results.
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
BrakemanApplication
<= 0.12CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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 Brakeman Plugin versionIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab and locate the Brakeman Plugin in the list. Note the version number displayed in the Version column.Affected if The displayed version is 0.12 or any version lower than 0.12 (e.g., 0.11, 0.10, etc.).
-
Verify plugin is actively usedSearch Jenkins job configurations for jobs that include the Brakeman post-build step. This can be done by navigating to each job's configuration page and looking for a 'Brakeman' build step or post-build action, or by searching configuration XML files for 'brakeman' references.Affected if Any job is configured to use the Brakeman plugin for scan results, making the XSS vulnerability reachable.
-
Locate Brakeman JSON result filesInspect the Jenkins job workspaces and build directories for files typically named 'brakeman' or 'brakeman-output' with .json extension, which are the scan result files that the plugin parses.Affected if JSON result files exist from Brakeman scans, as these are the files whose content gets rendered without proper escaping.
A user is affected if the Brakeman Plugin version is 0.12 or earlier AND the plugin is being used to process Brakeman scan results in any Jenkins job.
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 Brakeman Plugin version 0.12.1 or later, which properly escapes values received from parsed JSON files before rendering them in the web interface.
Fix this in Brakeman
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2122 — 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-2020-2122 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