Build PublisherApplication · Jenkins
CVE-2022-41232
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 (CSRF) vulnerability in Jenkins Build-Publisher Plugin 1.22 and earlier allows attackers to replace any config.xml file on the Jenkins controller file system with an empty file by providing a crafted file name to an API endpoint.
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-Publisher Plugin 1.22 and earlier allows attackers to replace any config.xml file on the Jenkins controller filesystem with an empty file by providing a crafted filename to an API endpoint, enabling denial of service or configuration disruption.
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 PublisherApplication
<= 1.22CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Verify Build-Publisher Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Build Publisher' or 'build-publisher' in the plugin list.Affected if Build Publisher plugin appears in the installed plugins list.
-
Check installed Build-Publisher versionIn the Installed Plugins tab, locate the Build Publisher entry and note the Version column. Compare this version number against the affected range: any version 1.22 or earlier is vulnerable.Affected if The installed version is 1.22 or lower.
-
Confirm API endpoint accessibilityCheck if the Build-Publisher API endpoint is exposed. This typically involves accessing a URL pattern such as /plugin/build-publisher/ or checking network exposure of the Jenkins API. Verify through Jenkins > Manage Jenkins > Configure Global Security what permissions are granted to anonymous or unauthenticated users for the API.Affected if The plugin API is accessible to unauthenticated or low-privilege users without additional authentication or network restrictions.
-
Verify CSRF protection statusNavigate to Jenkins > Manage Jenkins > Configure Global Security and locate the 'CSRF Protection' section. Confirm whethercrumb validation is enabled globally. Note: The fix in version 1.23 adds crumb validation specifically to the plugin's API endpoint.Affected if CSRF protection is disabled globally, or the Build-Publisher plugin API does not enforce crumb validation (version 1.22 or earlier).
You are affected if the Build-Publisher plugin is installed at version 1.22 or earlier and its API endpoint is accessible to attackers who could replace config.xml files.
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 dataUpdate to Build-Publisher Plugin version 1.23 or later which includes CSRF protection (crumb) validation. If immediate patching is not possible, restrict API access via network controls.
Fix this in Build Publisher
Scoped from the published advisory
- Consultation4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41232 — 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-2022-41232 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