JcloudsApplication · Jenkins
CVE-2019-10369
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 JClouds Plugin 2.14 and earlier in BlobStoreProfile.DescriptorImpl#doTestConnection and JCloudsCloud.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 confidenceMissing permission check in Jenkins JClouds Plugin allows users with only Overall/Read access to trigger the doTestConnection methods, enabling connection to attacker-specified URLs and retrieval of Jenkins-stored credentials using attacker-provided credential IDs.
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
JcloudsApplication
<= 2.14CVSS 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.
-
Verify JClouds Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'JClouds' or list installed plugins via CLI: jenkins-cli.jar or check $JENKINS_HOME/plugins/ for jclouds* directoriesAffected if JClouds plugin appears in the installed plugins list
-
Check installed JClouds Plugin versionIn Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed, find JClouds Plugin, and note the version column. Alternatively, inspect the plugin's manifest: $JENKINS_HOME/plugins/jclouds/META-INF/MANIFEST.MFAffected if Version is 2.14 or lower
-
Confirm Overall/Read permission existsNavigate to Manage Jenkins > Manage Users or check $JENKINS_HOME/users/ directory. Review configured authorization matrix or security realm to identify users or groups assigned Overall/Read permissionAffected if Any user or group is granted Overall/Read permission (this is the vulnerable permission level for this flaw)
-
Verify doTestConnection endpoint accessibilityAttempt a GET request to the JClouds plugin's test connection endpoint, typically under /plugin/jclouds/ or similar path, or inspect the plugin's routing configurationAffected if Request returns successfully without requiring elevated permissions beyond Overall/Read
User is affected if JClouds Plugin version 2.14 or lower is installed AND at least one user or group has Overall/Read permission configured, allowing unauthorized access to credential retrieval via the doTestConnection methods.
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 JClouds Plugin to version 2.15 or later which implements proper permission checks. Alternatively, restrict Overall/Read access until the upgrade can be applied.
Fix this in Jclouds
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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 $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10369 — 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-10369 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