Sonar Quality GatesApplication · Jenkins
CVE-2020-2150
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 · uneditedJenkins Sonar Quality Gates Plugin 1.3.1 and earlier transmits configured credentials in plain text as part of its global Jenkins configuration form, potentially resulting in their exposure.
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 confidenceThe Sonar Quality Gates Plugin for Jenkins versions 1.3.1 and earlier transmits user-configured credentials in plain text as part of the global Jenkins configuration form. This allows credentials to be exposed in transit, in logs, or to unauthorized users with access to the configuration interface.
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
Sonar Quality GatesApplication
<= 1.3.1CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Sonar Quality Gates Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Sonar Quality Gates', or inspect the plugin directory (typically $JENKINS_HOME/plugins/) for the sonar-quality-gates plugin folderAffected if The plugin appears in the installed plugins list or exists in the plugins directory
-
Identify the installed plugin versionIn Jenkins, click on the Sonar Quality Gates entry in the Installed tab to view its version, or locate the manifest file (MANIFEST.MF) inside the plugin's JAR file in the plugins directoryAffected if The version number shown is 1.3.1 or lower
-
Determine if credentials are configured in the pluginNavigate to Manage Jenkins > Configure System and locate the Sonar Quality Gates configuration section. Check whether any credentials fields (such as SonarQube token, username, or password) contain entered valuesAffected if Credentials fields contain any entered or saved values, even if they appear masked in the UI
-
Inspect the configuration form submission for plain text exposureUse browser developer tools (Network tab) to capture the HTTP request when saving the global configuration. Examine the request payload to see if credential values are transmitted in plain text rather than encrypted or maskedAffected if The submitted form data contains unencrypted credential strings in the request body
A user is affected if the Sonar Quality Gates Plugin version is 1.3.1 or lower AND credentials have been entered and saved in the plugin configuration.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate to a patched version of the Sonar Quality Gates Plugin that properly encrypts or masks credentials. If no patch is available, avoid storing credentials in this plugin or limit access to the global configuration page.
Fix this in Sonar Quality Gates
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2150 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-2150 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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