Skip to content
Fencer Intel
medium 4.0

CVE-2013-5676 json

Jenkins SonarQube Plugin Stores Passwords in Cleartext

published 12y ago modified last mo. also GHSA-3x9h-3p7m-33m7 , EUVD-2013-5514

cvss
4.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
5.0%
EPSS 5.0% chance of exploitation in 30 days, percentile 92%
public exploits
1
Exploit-DB

Summary

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.

Is CVE-2013-5676 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2013-5676 updated cvss 4.0

Plugin: Plain Text Password Disclosure via configuration parameters

  • Red Hat OpenShift Enterprise 1 jenkins Red Hat OpenShift Enterprise 2 jenkins
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. Published
  2. First public exploit (EDB-30409)

Exploit prediction

4.99% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-30409 SonarQube Jenkins Plugin - Plain Text Password webapps, 2013-12-18

CVSS scores

assigned by version score vector
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:P/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.jenkins-ci.plugins:sonar
<=3.7
 no fix listed

Classification

Weakness
  • CWE-310 Cryptographic Issues
  • CWE-312 Cleartext Storage of Sensitive Information

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.