# Jenkins Credentials plugin reveals encrypted values of credentials to users with Extended Read permission

Advisory record · `GHSA-62jv-j4w7-5hh8`

- **Identifiers:** `GHSA-62jv-j4w7-5hh8` · `CVE-2024-47805`
- **State:** Confirmed
- **Severity:** CVSS 4.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html) · [CWE-522](https://cwe.mitre.org/data/definitions/522.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [Hard-coded credentials](https://agentprime.io/advisories/tag/hard-coded-credentials.md)
- **Published:** 2 Oct 2024
- **Updated:** 13 Nov 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 2 Oct 2024, 18:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.jenkins-ci.plugins:credentials` (Maven): affected `>=1372, <1381.v2c3a || <1371.1373.v4eb`; fixed in `1381.v2c3a`, `1371.1373.v4eb`

## Machine-written summary

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

> Jenkins Credentials plugin versions 1380.va_435002fa_924 and earlier, excluding 1371.1373.v4eb_fa_b_7161e9, do not redact encrypted values of SecretBytes-type credentials such as certificate and secret file credentials when item config.xml is accessed via the REST API or CLI. An attacker with Item/Extended Read permission can view these encrypted values. Upgrade to Credentials plugin 1381.v2c3a or 1371.1373.v4eb, noting that the fix is only effective on Jenkins 2.479 and newer or LTS 2.462.3 and newer.

Written 8 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

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

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

## Timeline

- 31 Oct 2026, 15:13 UTC: First seen by agentprime
- 31 Oct 2026, 15:13 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-62jv-j4w7-5hh8)

## Sources

- [GitHub Advisory Database: GHSA-62jv-j4w7-5hh8](https://github.com/advisories/GHSA-62jv-j4w7-5hh8)
- [OSV: GHSA-62jv-j4w7-5hh8](https://osv.dev/vulnerability/GHSA-62jv-j4w7-5hh8)
- <https://nvd.nist.gov/vuln/detail/CVE-2024-47805>
- <https://www.jenkins.io/security/advisory/2024-10-02/#SECURITY-3373>

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-62jv-j4w7-5hh8>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-62jv-j4w7-5hh8/>. Everything for agents: <https://agentprime.io/llms.txt>.