# CVE-2013-6372: Jenkins Subversion Plugin Stores Credentials with Base64 Encoding

> Local attackers can read base64-encoded credentials from the Subversion plugin configuration file to obtain passwords and SSH keys.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 May 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-c4fr-gx5w-8qf2

## What is CVE-2013-6372?

CVE-2013-6372 is a low-severity vulnerability in n/a, published on 8 May 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-255

## Which versions are affected by CVE-2013-6372?

2 open source packages ship an affected version, including org.jenkins-ci.plugins:subversion. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:subversion` | Maven | All versions | 1.54 |
| `org.jenkins-ci.plugins:subversion` | Maven | All versions | 1.54 |

Products: Jenkins-Ci Subversion-Plugin.

## How do I fix CVE-2013-6372?

Upgrade org.jenkins-ci.plugins:subversion to 1.54 or later.

## Is CVE-2013-6372 being exploited?

There is no known exploitation of CVE-2013-6372 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-6372 and fix it if it is affected.

What it is: CVE-2013-6372 is a low-severity vulnerability in n/a, published on 8 May 2014. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-6372 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:subversion (Maven): affected all versions; fixed in 1.54
- org.jenkins-ci.plugins:subversion (Maven): affected all versions; fixed in 1.54

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-6372/ (Markdown: https://insights.sbomify.com/CVE-2013-6372/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-6372
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-6372
- OSV: https://osv.dev/vulnerability/CVE-2013-6372

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-6372/
Summaries are generated and may contain mistakes; the official description above is the record.