DockerApplication · Jenkins
CVE-2019-10341
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 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 missing permission check in Jenkins Docker Plugin 1.1.6 and earlier in DockerAPI.DescriptorImpl#doTestConnection allows users with Overall/Read access to connect to attacker-specified URLs using attacker-specified credentials IDs, enabling exfiltration of credentials stored in Jenkins.
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
- 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.
-
Identify if Jenkins Docker Plugin is installedIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab and look for 'Docker' in the list, or check the JENKINS_HOME/plugins directory for a docker.jpi or docker folder.Affected if Docker plugin is present in the Jenkins instance.
-
Determine the installed Docker Plugin versionIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab, find Docker plugin, and note the version number shown.Affected if Version is 1.1.6 or earlier.
-
Verify the doTestConnection endpoint is exposedAccess the Jenkins CLI or REST API endpoint at /descriptor/DockerAPI/doTestConnection (e.g., http://your-jenkins/descriptor/DockerAPI/doTestConnection). Alternatively, check if the Docker Cloud configuration page at /configureClouds/ has a 'Test Connection' button available.Affected if The endpoint responds or the Test Connection feature is available in the UI.
-
Check permission model for the affected endpointAttempt to access the doTestConnection endpoint or Test Connection feature using a test account that has only Overall/Read permission (no Administer or Overall/Admin rights).Affected if A user with only Overall/Read permission can successfully make a connection request to an arbitrary URL.
The environment is affected if Jenkins has Docker Plugin version 1.1.6 or earlier installed and users with only Overall/Read permission can access the doTestConnection functionality to make arbitrary network connections.
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 Docker Plugin to version 1.2.0 or later which implements proper permission checks on the doTestConnection method, restricting access to authorized users only.
Fix this in Docker
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-10341 — 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-10341 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