Cloud FoundryApplication · Jenkins
CVE-2019-1003025
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 exposure of sensitive information vulnerability exists in Jenkins Cloud Foundry Plugin 2.3.1 and earlier in AbstractCloudFoundryPushDescriptor.java that allows attackers 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 confidenceThe Jenkins Cloud Foundry Plugin versions 2.3.1 and earlier contain a vulnerability in AbstractCloudFoundryPushDescriptor.java that allows users with Overall/Read permissions to connect to attacker-controlled URLs using attacker-specified credential 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
Cloud FoundryApplication
<= 2.3.1CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 Cloud Foundry plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Cloud Foundry' in the list of installed pluginsAffected if The Cloud Foundry plugin appears in the installed plugins list
-
Identify the installed plugin versionIn the same Installed Plugins list, locate the Cloud Foundry plugin and note the Version column valueAffected if The version listed is 2.3.1 or any version number lower than 2.3.1
-
Confirm the plugin file version directlyCheck the plugin manifest file at <jenkins_home>/plugins/cloudfoundry/WEB-INF/MANIFEST.MF for the Implementation-Version attributeAffected if The Implementation-Version value is 2.3.1 or lower
-
Verify the vulnerable class existsInspect the plugin JAR file for the presence of AbstractCloudFoundryPushDescriptor.java compiled classes in the package structureAffected if The class org/jenkinsci/plugins/cloudfoundry/AbstractCloudFoundryPushDescriptor is present in the plugin
-
Check for exposed credential configurationsReview any Cloud Foundry cloud configurations under Manage Jenkins > Configure System > Cloud Foundry section to see if credentials are stored and configurableAffected if Cloud Foundry cloud configurations exist with stored credentials that could be specified by a user with Overall/Read access
If the Jenkins Cloud Foundry plugin is installed and its version is 2.3.1 or earlier, the environment is vulnerable to credential exfiltration via attacker-controlled URLs.
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 the Jenkins Cloud Foundry Plugin to a version newer than 2.3.1 and audit user permissions to limit Overall/Read access to only necessary personnel.
Fix this in Cloud Foundry
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1003025 — 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-1003025 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