Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

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

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

CVSS 4.3 MediumEPSS 0.0059 · 48th percentile

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.

PackageEcosystemAffectedFixed in
org.jenkins-ci.plugins:credentialsMaven>=1372, <1381.v2c3a || <1371.1373.v4eb1381.v2c3a, 1371.1373.v4eb
Identifiers
GHSA-62jv-j4w7-5hh8 · CVE-2024-47805
Weakness (CWE)
CWE-200 · CWE-522
Tags
Published
2 Oct 2024
Updated
13 Nov 2024

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

ScoreRatingCVSSVectorSource
4.3 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N 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

  1. 31 Oct 2026, 15:13 UTC First seen by agentprime
  2. 31 Oct 2026, 15:13 UTC Confirmed by OSV

Sources

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.