# Protection Mechanism Failure in Jenkins Script Security Plugin

Advisory record · `GHSA-784j-h234-m56x`

- **Identifiers:** `GHSA-784j-h234-m56x` · `CVE-2019-1003000`
- **State:** Confirmed
- **Severity:** CVSS 8.8 High
- **Critical:** Yes: CVSS 7+ and EPSS
- **Weakness (CWE):** [CWE-693](https://cwe.mitre.org/data/definitions/693.html)
- **Tags:** [CWE-693](https://agentprime.io/advisories/tag/cwe-693.md)
- **Published:** 13 May 2022
- **Updated:** 20 Feb 2024
- **Reviewed by a person:** No

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

## Critical

Critical, because:

- CVSS score 8.8 (7.0 or more) and EPSS 0.98 (0.1 or more): a high score and a real chance of exploitation in the next 30 days.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `org.jenkins-ci.plugins:script-security` (Maven): affected `<1.50`; fixed in `1.50`

## 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

- 8.8 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from GitHub Advisory Database

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

## Timeline

This record came from the full history of the GitHub Advisory Database, published 13 May 2022. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-784j-h234-m56x](https://github.com/advisories/GHSA-784j-h234-m56x)
- [OSV: GHSA-784j-h234-m56x](https://osv.dev/vulnerability/GHSA-784j-h234-m56x)
- <https://nvd.nist.gov/vuln/detail/CVE-2019-1003000>
- <https://github.com/jenkinsci/script-security-plugin/commit/2c5122e50742dd16492f9424992deb21cc07837c>
- <https://access.redhat.com/errata/RHBA-2019:0326>
- <https://access.redhat.com/errata/RHBA-2019:0327>
- <https://jenkins.io/security/advisory/2019-01-08/#SECURITY-1266>
- <https://www.exploit-db.com/exploits/46453>
- <https://www.exploit-db.com/exploits/46572>
- <http://packetstormsecurity.com/files/152132/Jenkins-ACL-Bypass-Metaprogramming-Remote-Code-Execution.html>
- <http://www.rapid7.com/db/modules/exploit/multi/http/jenkins_metaprogramming>

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-784j-h234-m56x>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-784j-h234-m56x/>. Everything for agents: <https://agentprime.io/llms.txt>.