dbcve.org
Sonarqube ScannerApplication · Sonarsource

CVE-2018-1000425

HIGH · 7.8 CVSS v3.0 Published 2019-01-09
Fix available
A fix is available. Upgrade to after 2.8 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An insufficiently protected credentials vulnerability exists in Jenkins SonarQube Scanner Plugin 2.8 and earlier in SonarInstallation.java that allows attackers with local file system access to obtain the credentials used to connect to SonarQube.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The SonarQube Scanner Plugin for Jenkins versions 2.8 and earlier stores credentials used to connect to SonarQube in an insecure manner in SonarInstallation.java. An attacker with local file system access to the Jenkins controller or agent can read these credentials from the configuration files.

MitigationUpgrade the Jenkins SonarQube Scanner Plugin to version 2.8.1 or later. If upgrade is not immediately possible, restrict local file system access to the Jenkins home directory and ensure proper file permissions are in place.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Sonarqube ScannerApplication
Affected:<= 2.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify SonarQube Scanner Plugin version
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and look for 'SonarQube Scanner' in the list, or check the version file in $JENKINS_HOME/plugins/sonar/WEB-INF/manifest.mf
    Affected if The version listed is 2.8 or earlier
  2. Check if SonarQube credentials are configured
    Look for SonarQube server configuration in $JENKINS_HOME/org.jenkinsci.plugins.sonar.SonarGlobalConfiguration.xml or via Jenkins UI at Manage Jenkins > Configure System > SonarQube configuration section
    Affected if A SonarQube server is configured with credentials stored in these XML configuration files
  3. Inspect credential storage format
    Open the SonarQube configuration XML file and examine whether credentials (username/password or token) appear in plain text rather than being encrypted or using Jenkins credentials binding
    Affected if Credentials appear in plaintext within the XML configuration file
  4. Verify file permissions on configuration
    Check file permissions on $JENKINS_HOME/org.jenkinsci.plugins.sonar.SonarGlobalConfiguration.xml using 'ls -la' - ensure other users cannot read this file
    Affected if File permissions allow read access by non-privileged users (world-readable or group-readable)
  5. Check plugin metadata for version
    If accessing the plugins directory directly, examine $JENKINS_HOME/plugins/sonar/META-INF/MANIFEST.MF for the Plugin-Version attribute
    Affected if The Plugin-Version value is 2.8 or lower

A user is affected if the SonarQube Scanner Plugin version is 2.8 or earlier AND SonarQube credentials are configured in plaintext within Jenkins configuration files accessible to unauthorized local users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 2.8
Interim mitigation

Upgrade the Jenkins SonarQube Scanner Plugin to version 2.8.1 or later. If upgrade is not immediately possible, restrict local file system access to the Jenkins home directory and ensure proper file permissions are in place.

Fix this in Sonarqube Scanner Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1000425 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-1000425 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data