Home/CVE/Jenkins Credentials Plugin 1380.va_435002fa_924 and earlier, except 1371.1373.v4eb_fa_b_7161e9, does not redact encrypte
CVE
CVE-2024-47805
Jenkins Credentials Plugin 1380.va_435002fa_924 and earlier, except 1371.1373.v4eb_fa_b_7161e9, does not redact encrypte
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.
HIGH · CVSS 7.5
EPSS 0.00583
Act now
- Public exploit or PoC is available
- SSVC automatable: yes - attacks can be scripted at scale
- CVSS base score ≥ 7.0
Sigma rules8
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2024-47805, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
◆
ATT&CK techniques
12Techniques this CVE enables - linked via CWECAPECATT&CK. High◆ = named directly in ATT&CK or Nuclei templates.
T1021 · Remote Services T1021.002 · SMB/Windows Admin Shares T1078 · Valid Accounts T1110.004 · Credential Stuffing T1114.002 · Remote Email Collection T1133 · External Remote Services T1543 · Create or Modify System Process T1550.002 · Pass the Hash T1550.003 · Pass the Ticket T1552.004 · Private Keys T1558 · Steal or Forge Kerberos Tickets T1558.003 · Kerberoasting
▤ Build a SIEM detection for these techniques
▤
CAPEC attack patterns
12Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.
CAPEC-CAPEC-102 · Session Sidejacking CAPEC-CAPEC-474 · Signature Spoofing by Key Theft CAPEC-CAPEC-50 · Password Recovery Exploitation CAPEC-CAPEC-509 · Kerberoasting CAPEC-CAPEC-551 · Modify Existing Service CAPEC-CAPEC-555 · Remote Services with Stolen Credentials CAPEC-CAPEC-560 · Use of Known Domain Credentials CAPEC-CAPEC-561 · Windows Admin Shares with Stolen Credentials CAPEC-CAPEC-600 · Credential Stuffing CAPEC-CAPEC-644 · Use of Captured Hashes (Pass The Hash) CAPEC-CAPEC-645 · Use of Captured Tickets (Pass The Ticket) CAPEC-CAPEC-652 · Use of Known Kerberos Credentials
⬡
Weakness Classification
▤
Affected Products & Versions
2jenkins credentials< 1371.1373.v4eb_fa_b_7161e9
jenkins credentials>= 1371.vfee6b_095f0a_3 and < 1380.va_435002fa_924
▤
Affected Packages
1Language-ecosystem packages (from OSV) tied to this CVE, with the version that fixes it - the dependency-level detail NVD doesn’t carry.
Maven
org.jenkins-ci.plugins:credentials
MODERATE
fixed in 1381.v2c3a
⚠
Public Exploits & PoCs
1These PoC and exploit links come from public sources and are not verified to be safe or functional. Review the code before running anything, and treat unverified entries as untrusted. Signed-in users rate each one out of 10 (does it actually work) and can flag malware.
◈
Sigma Hunt Rules
8Exact rules name this CVE ID. Product rules name an affected product in their title. Related rules cover techniques used by actors who exploited this CVE. Showing the most relevant matches; the complete related set is on the full drill-down.
producthighCredentials In Files
producthighMalicious Usage Of IMDS Credentials Outside Of AWS Infrastructure
producthighAdded Credentials to Existing Application
producthighCredentials In Files - Linux
producthighVeeamBackup Database Credentials Dump Via Sqlcmd.EXE
producthighHackTool - Pypykatz Credentials Dumping Activity
▣
Scoring & Timeline
7.5
HIGH · CVSS v3.1 · [email protected]
Attack Vector
Network
Adjacent
Local
Physical
Attack Complexity
Low
High
Privileges Required
None
Low
High
User Interaction
None
Required
Scope
Unchanged
Changed
Confidentiality
None
Low
High
Integrity
None
Low
High
Availability
None
Low
High
SSVC triage · cisa-vulnrichment
Exploitation
none
Automatable
yes
Technical impact
partial
SSVC asks the questions that actually drive patch urgency: is it being exploited, can attacks be automated, and how total is the impact.
🔗
References & Sources
1Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.