dbcve.org
CredentialsApplication · Jenkins

CVE-2024-47805

HIGH · 7.5 CVSS v3.1 Published 2024-10-02
Fix available
A fix is available. Upgrade to 1371.1373.v4eb_fa_b_7161e9 / 1380.va_435002fa_924 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Jenkins Credentials Plugin 1380.va_435002fa_924 and earlier, except 1371.1373.v4eb_fa_b_7161e9, does not redact encrypted values of credentials using the `SecretBytes` type when accessing item `config.xml` via REST API or CLI.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Jenkins Credentials Plugin versions 1380.va_435002fa_924 and earlier fail to redact encrypted credential values of the SecretBytes type when item config.xml is accessed via REST API or CLI, allowing unauthorized disclosure of sensitive credential data.

MitigationUpgrade to the patched version of Jenkins Credentials Plugin (1380.va_435002fa_924 or later, excluding 1371.1373.v4eb_fa_b_7161e9) or restrict API/CLI access to trusted users only until patching is feasible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CredentialsApplication
Affected:< 1371.1373.v4eb_fa_b_7161e9>= 1371.vfee6b_095f0a_3, < 1380.va_435002fa_924

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Jenkins Credentials Plugin version
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, or use the CLI command: java -jar jenkins-cli.jar plugin credentials 2>/dev/null; alternatively check $JENKINS_HOME/plugins/credentials/META-INF/MANIFEST.MF for the plugin version
    Affected if Version is 1380.va_435002fa_924 or earlier, specifically in the ranges < 1371.1373.v4eb_fa_b_7161e9 or >= 1371.vfee6b_095f0a_3 and < 1380.va_435002fa_924
  2. Verify SecretBytes credentials exist
    Use the Jenkins UI: Manage Jenkins > Manage Credentials > look for credentials with type 'Secret bytes' or query the credentials store via API: /credentials/store/system/domain/_/api/json
    Affected if Any credentials of type SecretBytes (Secret bytes) are stored in Jenkins
  3. Confirm REST API access to config.xml
    Make a GET request to /job/JOBNAME/config.xml (with authentication credentials that have job read permissions)
    Affected if API request returns unredacted credential data in the XML response, specifically values that appear as <secretBytes> elements with actual base64-encoded content instead of masked values
  4. Verify CLI access to config.xml
    Use Jenkins CLI: java -jar jenkins-cli.jar get-job JOBNAME -i <user-key> or similar CLI command to retrieve job configuration
    Affected if CLI returns unredacted SecretBytes credential values in the output

Your environment is affected if the Credentials Plugin version falls in the vulnerable range AND you have SecretBytes credentials stored AND API or CLI access to job config.xml is available to users without full credential permissions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1371.1373.v4eb_fa_b_7161e9 / 1380.va_435002fa_924 or later
Fixed in 1371.1373.v4eb_fa_b_7161e91380.va_435002fa_924
Interim mitigation

Upgrade to the patched version of Jenkins Credentials Plugin (1380.va_435002fa_924 or later, excluding 1371.1373.v4eb_fa_b_7161e9) or restrict API/CLI access to trusted users only until patching is feasible.

Recommended fix High confidence

1380.va_435002fa_924 or later

  1. 1. Back up your Jenkins instance and configuration
  2. 2. Navigate to Manage Jenkins > Manage Plugins
  3. 3. Go to the 'Updates' tab
  4. 4. Locate the Credentials Plugin in the list
  5. 5. Select the plugin and click 'Update'
  6. 6. Restart Jenkins to apply the update
  7. 7. Alternatively, download the updated .hpi file from the Jenkins plugin repository and install via 'Advanced' > 'Upload Plugin'

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Credentials Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47805 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-47805 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data