# CVE-2013-6373: Jenkins Exclusion Plugin allows Access to Resource Locks

> Authenticated users can bypass access controls to list and release resource locks in the Jenkins Exclusion plugin.

- **Severity:** Medium 5.5 (`AV:N/AC:L/Au:S/C:P/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Nov 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-2q8v-439j-6p77

## What is CVE-2013-6373?

CVE-2013-6373 is a medium-severity missing authorization vulnerability in n/a, published on 25 Nov 2013. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Exclusion plugin before 0.9 for Jenkins does not properly prevent access to resource locks, which allows remote authenticated users to list and release resources via unspecified vectors.

Weakness: CWE-264

## Which versions are affected by CVE-2013-6373?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:exclusion` | Maven | All versions | 0.9 |
| `org.jenkins-ci.plugins:exclusion` | Maven | All versions | 0.9 |

Products: Jenkins-Ci Exclusion.

## How do I fix CVE-2013-6373?

Upgrade org.jenkins-ci.plugins:exclusion to 0.9 or later.

## Is CVE-2013-6373 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-6373 and fix it if it is affected.

What it is: CVE-2013-6373 is a medium-severity missing authorization vulnerability in n/a, published on 25 Nov 2013. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-6373 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:exclusion (Maven): affected all versions; fixed in 0.9
- org.jenkins-ci.plugins:exclusion (Maven): affected all versions; fixed in 0.9

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-2013-6373/ (Markdown: https://insights.sbomify.com/CVE-2013-6373/index.md)
```

## Sources

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

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