# CVE-2013-5676: Jenkins SonarQube Plugin Stores Passwords in Cleartext

> Authenticated users can read cleartext SonarQube passwords from Jenkins configuration, exposing sensitive credentials.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Dec 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3x9h-3p7m-33m7

## What is CVE-2013-5676?

CVE-2013-5676 is a medium-severity vulnerability in n/a, published on 13 Dec 2013. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Jenkins Plugin for SonarQube 3.7 and earlier allows remote authenticated users to obtain sensitive information (cleartext passwords) by reading the value in the sonar.sonarPassword parameter from jenkins/configure.

Weakness: CWE-310

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:sonar` | Maven | All versions to 3.7 | None |
| `org.jenkins-ci.plugins:sonar` | Maven | All versions to 3.7 | None |

Products: Sonarsource Jenkins Plugin.

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

No fix has been published for CVE-2013-5676 yet. Limit exposure of the affected software until one is available.

## Is CVE-2013-5676 being exploited?

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

Public exploit code:

- SonarQube Jenkins Plugin - Plain Text Password (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-5676 is a medium-severity vulnerability in n/a, published on 13 Dec 2013. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-5676 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:sonar (Maven): affected all versions up to 3.7; no fix listed
- org.jenkins-ci.plugins:sonar (Maven): affected all versions up to 3.7; no fix listed

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-5676/ (Markdown: https://insights.sbomify.com/CVE-2013-5676/index.md)
```

## Sources

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

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