# Jenkins Exclusion Plugin allows Access to Resource Locks

Advisory record · `GHSA-2q8v-439j-6p77`

- **Identifiers:** `GHSA-2q8v-439j-6p77` · `CVE-2013-6373`
- **State:** Confirmed
- **Severity:** CVSS 4.0, no score published
- **Critical:** No
- **Weakness (CWE):** [CWE-284](https://cwe.mitre.org/data/definitions/284.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 17 May 2022
- **Updated:** 13 Mar 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 17 May 2022, 03:51 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.jenkins-ci.plugins:exclusion` (Maven): affected `<0.9`; fixed in `0.9`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Jenkins Exclusion Plugin (org.jenkins-ci.plugins:exclusion) before 0.9 does not properly restrict access to resource locks. A remote authenticated user can list and release those resources through unspecified vectors. Upgrade to version 0.9 or later.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- Score not published, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.011, the 67th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:11 UTC: First seen by agentprime
- 31 Oct 2026, 15:11 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-2q8v-439j-6p77)

## Sources

- [GitHub Advisory Database: GHSA-2q8v-439j-6p77](https://github.com/advisories/GHSA-2q8v-439j-6p77)
- [OSV: GHSA-2q8v-439j-6p77](https://osv.dev/vulnerability/GHSA-2q8v-439j-6p77)
- <https://nvd.nist.gov/vuln/detail/CVE-2013-6373>
- <https://github.com/jenkinsci/exclusion-plugin/commit/847f9aeb407c0f47046d184080c9e2c2e3720311>
- <https://github.com/jenkinsci/exclusion-plugin>
- <https://wiki.jenkins-ci.org/display/JENKINS/Exclusion-Plugin>
- <https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2013-11-20>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-2q8v-439j-6p77>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-2q8v-439j-6p77/>. Everything for agents: <https://agentprime.io/llms.txt>.
