BazaarApplication · Jenkins
CVE-2023-39156
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 Bazaar Plugin 1.22 and earlier allows attackers to delete previously created Bazaar SCM tags.
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 Bazaar Plugin versions 1.22 and earlier allows remote attackers to trick authenticated users into unknowingly deleting previously created Bazaar SCM tags through forged HTTP requests.
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
BazaarApplication
<= 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Verify Bazaar Plugin is installedNavigate to Jenkins dashboard > Manage Jenkins > Manage Plugins > Installed tab. Search for 'Bazaar' in the filter. Confirm the plugin appears in the list.Affected if The Bazaar plugin is not present in the installed plugins list, meaning the plugin is not installed and this CVE does not apply.
-
Locate the installed Bazaar Plugin versionIn the same Installed plugins tab, find the Bazaar plugin entry. The version number is displayed in the Version column next to the plugin name.Affected if The version column shows a version number for the Bazaar plugin.
-
Compare installed version to affected rangeCompare the version number found in the previous step to the affected range. The vulnerable range is version 1.22 and earlier. Any version <= 1.22 is affected.Affected if The installed version is 1.22 or lower (for example: 1.22, 1.21, 1.20, etc.). This indicates the plugin is vulnerable to CVE-2023-39156.
-
Confirm authentication context requirementUnderstand that this CSRF vulnerability requires an authenticated user with permissions to manage Bazaar SCM tags. Check if any users have Bazaar-related permissions in Jenkins.Affected if Authenticated users with Bazaar SCM tag management permissions exist in the Jenkins environment, making the CSRF attack vector viable.
The environment is affected if the Bazaar Plugin is installed with version 1.22 or earlier and there are authenticated users with permissions to manage Bazaar SCM tags.
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 a patched version of the Bazaar Plugin that implements proper CSRF token validation, or if no fix is available, disable the plugin until remediation is possible.
Fix this in Bazaar
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-39156 — 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-2023-39156 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