KmapApplication · Jenkins
CVE-2019-10293
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 · uneditedA missing permission check in Jenkins Kmap Plugin in KmapJenkinsBuilder.DescriptorImpl form validation methods allows attackers with Overall/Read permission to initiate a connection to an attacker-specified server.
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's form validation methods lack proper permission checks, allowing any user with Overall/Read permission to trigger the plugin to initiate network connections to attacker-specified servers. This is a Server-Side Request Forgery (SSRF) vulnerability resulting from missing authorization on validation endpoints.
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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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.
-
Confirm Kmap plugin installationNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Kmap', or use Jenkins CLI: java -jar jenkins-cli.jar -s http://[jenkins-url] list-plugins | grep -i kmapAffected if The Kmap plugin appears in the list of installed plugins
-
Verify Overall/Read permission is enabledGo to Jenkins > Manage Jenkins > Configure Global Security > Authorization and check if any users or groups are granted the Overall/Read permission, or if anonymous read access is enabledAffected if Any user (including anonymous) has Overall/Read permission to access Jenkins
-
Identify form validation endpointsReview the Kmap plugin's configuration pages (typically under Job or Configure steps that use Kmap) and note any form fields that trigger network validation, or inspect HTTP access logs for requests to endpoints containing '/descriptorByName/' and 'kmap'Affected if The Kmap plugin exposes form validation methods that initiate outbound network connections
-
Check plugin version against fixIn Manage Plugins > Installed, click on the Kmap plugin and view the Version field; the fix was introduced in a version released after the CVE publication dateAffected if The installed version is older than the patched version containing permission checks
If the Kmap plugin is installed and any user has Overall/Read permission, the environment is vulnerable to SSRF through the plugin's unauthenticated form validation endpoints.
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 dataApply the latest plugin update containing the permission check fix, or manually add appropriate permission validation (e.g., using Jenkins' permissionCheck() or equivalent) to all DescriptorImpl form validation methods before allowing outbound connections.
Fix this in Kmap
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10293 — 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-10293 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