DockerApplication · Jenkins
CVE-2019-10340
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 cross-site request forgery vulnerability in Jenkins Docker Plugin 1.1.6 and earlier in DockerAPI.DescriptorImpl#doTestConnection allowed users with Overall/Read access to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.
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 confidenceA CSRF vulnerability in Jenkins Docker Plugin 1.1.6 and earlier in the DockerAPI.DescriptorImpl#doTestConnection endpoint allows users with Overall/Read access to connect to attacker-specified URLs using attacker-specified credentials IDs, enabling exfiltration of stored Jenkins 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
DockerApplication
<= 1.1.6CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 Docker plugin is installedIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab and search for 'Docker' in the list of installed pluginsAffected if The Docker plugin appears in the installed plugins list
-
Check Docker plugin versionIn the same Installed plugins list, note the version number displayed next to the Docker pluginAffected if The version is 1.1.6 or earlier (e.g., 1.1.6, 1.1.5, 1.1.4, etc.)
-
Verify Overall/Read permission is enabledGo to Manage Jenkins > Configure Global Security > Authorization section and check if 'Overall/Read' permission is granted to the relevant user or group (such as 'Authenticated Users' or 'Everyone')Affected if Users or groups have Overall/Read access enabled, which allows access to the vulnerable endpoint
-
Confirm vulnerable endpoint existsAttempt to access the Docker plugin test connection endpoint at /descriptor/DockerAPI.DescriptorImpl/doTestConnection or verify through plugin configuration that Docker cloud configuration is availableAffected if The DockerAPI descriptor endpoint is accessible and accepts connection test requests
If the Docker plugin version is 1.1.6 or earlier AND users have Overall/Read access, the environment is vulnerable to CVE-2019-10340
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 Jenkins Docker Plugin to version 1.1.7 or later. Ensure Jenkins crumb-based CSRF protection is enabled as an additional safeguard.
Fix this in Docker
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10340 — 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-10340 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