KmapApplication · Jenkins
CVE-2019-10294
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 Kmap 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 Kmap Plugin stores credentials in plaintext within job config.xml files on the Jenkins master filesystem. Users with Extended Read permission (a built-in Jenkins permission allowing read access to job configurations) or anyone with filesystem access to the Jenkins master can view these unencrypted credentials directly from the XML files.
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
KmapApplication
all versionsCVSS 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 Kmap Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed and search for 'Kmap' or check the plugin directory $JENKINS_HOME/plugins for the kmap plugin folderAffected if The Kmap plugin appears in the installed plugins list
-
Identify jobs using Kmap configurationSearch job config.xml files for '<kmap>' or 'org.jenkinsci.plugins.kmap' XML elements, or manually review jobs that use Kmap for mapping credentialsAffected if Any job config.xml contains '<kmap>' configuration blocks
-
Check for plaintext credentials in config.xmlExamine the raw XML of affected job config.xml files (located in $JENKINS_HOME/jobs/<jobname>/config.xml) and look for credential values stored as plaintext string values within kmap elements rather than <credentialsId> referencesAffected if config.xml files contain visible plaintext passwords or API keys within kmap configuration elements
-
Review Extended Read permission assignmentsGo to Manage Jenkins > Manage Users and check which users or groups have the Extended Read permission (typically found in matrix authorization or logged-in users can read)Affected if Users beyond administrators have Extended Read permission enabled
-
Assess filesystem access to config.xmlVerify file permissions on $JENKINS_HOME/jobs/*/config.xml files - check if non-admin users or processes can read these filesAffected if File permissions allow reading config.xml files by users other than the Jenkins service account
A user is affected if the Kmap plugin is installed, any job configuration contains plaintext credentials in kmap XML elements, and either Extended Read permission is granted to non-admin users or filesystem access to config.xml files is not properly restricted.
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 dataRestrict Extended Read permission to only trusted users, remove any credentials stored via this plugin from config.xml files, and update to a patched version of the Kmap Plugin that properly encrypts credentials.
Fix this in Kmap
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10294 — 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-10294 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