Sonar GerritApplication · Jenkins
CVE-2019-10467
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 Gerrit Plugin stores credentials unencrypted in job config.xml files on the Jenkins master where they can be viewed by users with Extended Read permission, or access to the master file system.
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 Jenkins Sonar Gerrit Plugin stores user credentials in plaintext within job config.xml files on the Jenkins master. This occurs because the plugin does not encrypt these credentials before saving them to the configuration. Users with Extended Read permission on Jenkins jobs, or anyone with file system access to the Jenkins master, can view these unencrypted credentials.
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 GerritApplication
<= 2.3CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 Gerrit Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Sonar Gerrit' or inspect the plugin directory if accessibleAffected if The plugin is installed and its version is 2.3 or lower
-
Identify jobs using Sonar Gerrit pluginSearch job config.xml files for the presence of '<sonarGerrit>' or related XML elements that indicate the Sonar Gerrit plugin is configured for a jobAffected if Any Jenkins job has the Sonar Gerrit plugin configured in its configuration
-
Inspect job config.xml for plaintext credentialsOpen the config.xml file for each job using the Sonar Gerrit plugin and search for credential fields containing actual username/password values in plaintext rather than encrypted credential IDsAffected if The config.xml contains visible username and password strings in fields used by the Sonar Gerrit plugin configuration
-
Verify Extended Read permission exposureReview Jenkins matrix-based security or project-based matrix authorization settings to identify which users or groups have Extended Read permission on affected jobsAffected if Users other than administrators have Extended Read permission on jobs that store credentials via this plugin
You are affected if the Sonar Gerrit Plugin version 2.3 or lower is installed AND any job configuration contains plaintext credentials in the Sonar Gerrit section of config.xml files.
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 dataCredentials stored by the plugin should be encrypted using Jenkins' built-in credential storage mechanisms. Administrators should rotate any credentials that may have been exposed and restrict access to config.xml files. Users with Extended Read permission should be limited to only those who require it.
Fix this in Sonar Gerrit
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10467 — 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-2019-10467 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