Azure AdApplication · Jenkins
CVE-2019-10318
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 Azure AD Plugin 0.3.3 and earlier stored the client secret unencrypted in the global config.xml configuration file on the Jenkins master where it could be viewed by users with 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 Azure AD Plugin for Jenkins versions 0.3.3 and earlier stores the OAuth client secret in plaintext within the global config.xml configuration file on the Jenkins master. Any user with access to the Jenkins master file system can read this file and obtain the plaintext client secret, leading to unauthorized Azure AD authentication.
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
Azure AdApplication
<= 0.3.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
- High
- Availability
- High
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Azure AD plugin is installedUse Jenkins CLI: jenkins-cli.jar who-is-online or check $JENKINS_HOME/plugins/ for azure-ad directoryAffected if The azure-ad plugin directory exists in the Jenkins plugins folder
-
Check plugin versionInspect the $JENKINS_HOME/plugins/azure-ad/META-INF/MANIFEST.MF file for the Plugin-Version attributeAffected if The version listed is 0.3.3 or lower
-
Locate the global configuration fileFind the Jenkins config.xml file, typically at $JENKINS_HOME/config.xmlAffected if The config.xml file exists on the Jenkins master filesystem
-
Inspect for plaintext OAuth client secretOpen config.xml and search for <clientSecret> or similar XML elements containing the Azure AD OAuth client secret valueAffected if A <clientSecret> element contains an actual secret value in plaintext (not masked or encrypted)
-
Verify credential storage methodCheck if the secret appears in plain text versus being stored as a credential ID reference (typically looks like ${some-uuid})Affected if The clientSecret field contains a readable string value rather than a credential ID reference
A user is affected if the Azure AD plugin version is 0.3.3 or lower AND the config.xml file contains a plaintext OAuth client secret in the 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 dataUpgrade to a patched version of the Azure AD plugin and immediately rotate any exposed client secrets. Consider using Jenkins credential storage mechanisms for sensitive values rather than storing them in config files.
Fix this in Azure Ad
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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 $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10318 — 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-10318 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