Build PublisherApplication · Jenkins
CVE-2022-41231
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 Build-Publisher Plugin 1.22 and earlier allows attackers with Item/Configure permission to create or replace any config.xml file on the Jenkins controller file system 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 confidenceThe Jenkins Build-Publisher Plugin versions 1.22 and earlier contains a path traversal vulnerability in its API endpoint. Attackers with Item/Configure permission can craft a malicious file name to write or replace arbitrary config.xml files anywhere on the Jenkins controller file system, potentially leading to configuration tampering or denial of service.
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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/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 if Build-Publisher Plugin is installedAccess the Jenkins script console at /script or use the CLI to list installed plugins. Run: Jenkins.instance.pluginManager.plugins.collect { it.shortName + ': ' + it.version }. Look for 'build-publisher' in the output.Affected if The plugin is installed and its version is 1.22 or earlier.
-
Confirm the exact version of Build-Publisher PluginIn the Jenkins web UI, navigate to Manage Jenkins > Manage Plugins > Installed tab. Locate Build-Publisher in the list and note the version number displayed.Affected if Version is 1.22 or lower.
-
Check if the API endpoint is accessibleThe vulnerable endpoint is the plugin's API that accepts file name parameters. Verify network access to Jenkins from untrusted sources is permitted, as exploitation requires network access to the Jenkins API.Affected if The Jenkins API is exposed to users with Item/Configure permission who should not have that access.
-
Review Item/Configure permission assignmentsIn Jenkins, go to Manage Jenkins > Manage Users and check which users or groups have Item/Configure permission. This permission is required for exploitation. Identify if any untrusted users or groups possess this permission.Affected if Untrusted or anonymous users have Item/Configure permission.
A user is affected if the Build-Publisher Plugin version 1.22 or earlier is installed and untrusted users have Item/Configure permission, allowing them to access the vulnerable API endpoint.
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 the Build-Publisher Plugin to version 1.23 or later which contains the fix for the path traversal vulnerability. Alternatively, restrict Item/Configure permission to trusted users only until the upgrade can be performed.
Fix this in Build Publisher
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41231 — 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-41231 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