# CVE-2023-39156: CSRF vulnerability in Bazaar Plugin

> Attackers can trick users into deleting Bazaar SCM tags via CSRF, requiring plugin updates to mitigate.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jul 2023
- **Updated:** 23 Oct 2024
- **Also known as:** GHSA-6f4q-f5fj-q6fc

## What is CVE-2023-39156?

CVE-2023-39156 is a medium-severity vulnerability in Jenkins Bazaar Plugin, published on 26 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A cross-site request forgery (CSRF) vulnerability in Jenkins Bazaar Plugin 1.22 and earlier allows attackers to delete previously created Bazaar SCM tags.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2023-39156?

2 open source packages ship an affected version, including org.jenkins-ci.plugins:bazaar. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:bazaar` | Maven | All versions to 1.22 | None |
| `org.jenkins-ci.plugins:bazaar` | Maven | All versions to 1.22 | None |

Products: Jenkins Bazaar.

## How do I fix CVE-2023-39156?

No fix has been published for CVE-2023-39156 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-39156 being exploited?

There is no known exploitation of CVE-2023-39156 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-39156 and fix it if it is affected.

What it is: CVE-2023-39156 is a medium-severity vulnerability in Jenkins Bazaar Plugin, published on 26 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-39156 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:bazaar (Maven): affected all versions up to 1.22; no fix listed
- org.jenkins-ci.plugins:bazaar (Maven): affected all versions up to 1.22; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-39156/ (Markdown: https://insights.sbomify.com/CVE-2023-39156/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-39156
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-39156
- OSV: https://osv.dev/vulnerability/CVE-2023-39156

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-39156/
Summaries are generated and may contain mistakes; the official description above is the record.