dbcve.org
JcloudsApplication · Jenkins

CVE-2019-10368

HIGH · 8.8 CVSS v3.0 Published 2019-08-07
Fix available
A fix is available. Upgrade to after 2.14 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
A cross-site request forgery vulnerability 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 confidence

A CSRF vulnerability in Jenkins JClouds Plugin versions 2.14 and earlier allowed users with Overall/Read access to trigger connection tests to attacker-controlled URLs using attacker-specified credentials IDs, enabling exfiltration of stored Jenkins credentials.

MitigationUpgrade JClouds Plugin to version 2.15 or later which includes CSRF protection tokens. Alternatively, disable the plugin until patching is feasible.

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
Affected:<= 2.14

CVSS 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.0/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify JClouds Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'JClouds' or 'jclouds', or use the CLI: java -jar jenkins-cli.jar list-plugins 2>/dev/null | grep -i jclouds
    Affected if JClouds plugin appears in the plugin list
  2. Check installed JClouds Plugin version
    In the Installed tab of Manage Plugins, find the version number next to JClouds Plugin, or use: curl -s http://JENKINS_URL/pluginManager/plugin/jclouds/installed -H 'Jenkins-Crumb:...' | grep -o 'version="[^"]*"' (or check plugin manifest in $JENKINS_HOME/plugins/jclouds/META-INF/MANIFEST.MF)
    Affected if Version is 2.14 or earlier, or version cannot be determined (indicating outdated release)
  3. Confirm plugin is enabled and loaded
    Check that the JClouds plugin is not disabled in Manage Plugins > Installed, and verify no errors in Manage Jenkins > System Information related to jclouds plugin loading
    Affected if Plugin shows as enabled and loads without errors in Jenkins
  4. Verify user access configuration
    Check if any users or groups have Overall/Read permission in Manage Jenkins > Manage Users and Manage Jenkins > Configure Global Security > Authorization (default installations grant Overall/Read to all authenticated users)
    Affected if Users have Overall/Read access (this is the default anonymous or authenticated user baseline)
  5. Check for cloud provider configurations
    Navigate to Manage Jenkins > Manage Clouds (or Configure Clouds) and look for any JClouds cloud configurations that could be tested via connection tests
    Affected if Any JClouds cloud configurations exist that could be tested via the vulnerable endpoint

If JClouds Plugin version 2.14 or earlier is installed, enabled, and users have Overall/Read access (common default), the environment is affected by this CSRF vulnerability allowing credential exfiltration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 2.14
Interim mitigation

Upgrade JClouds Plugin to version 2.15 or later which includes CSRF protection tokens. Alternatively, disable the plugin until patching is feasible.

Fix this in Jclouds Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,540
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-10368 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-10368 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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