CVE-2013-6372: The Subversion plugin before 1.54 for Jenkins stores credentials using base64 encoding, which allows local use
CVE-2013-6372 is a low-severity flaw (CVSS 2.1) affecting subversion-plugin. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The Subversion plugin before 1.54 for Jenkins stores credentials using base64 encoding, which allows local users to obtain passwords and SSH private keys by reading a subversion.credentials file.
Why this priority
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 2.1 (Low) |
| EPSS exploit chance | 0.5% (top 57%) |
| CISA exploited list | No |
| Weakness | CWE-255 |
| Published | 2014-05-08 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2013-6372?
subversion-plugin: upgrade to newer than 1.53. Exact commands for each OS are on this page.
Is CVE-2013-6372 being exploited?
CVE-2013-6372 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2013-6372 affect?
CVE-2013-6372 affects subversion-plugin. Severity is low (CVSS 2.1). The Subversion plugin before 1.54 for Jenkins stores credentials using base64 encoding, which allows local users to obtain passwords and SSH private keys by reading a subversion.credentials file.
How urgent is CVE-2013-6372?
Priority 23/100. Public exploit reference