Java Projects using HTTP to fetch dependencies
Cloud Foundry cf-deployment, versions prior to 7.9.0, contain java components that are using an insecure protocol to fetch dependencies when building. A remote unauthenticated malicious attacker could hijack the DNS entry for the dependency, and inject malicious code into the component.
- Published
- Apr 25, 2019
- Updated
- Jun 16, 2026
- EPSS
- 0.6% · 46th percentile
- CWE
- CWE-494
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
39
Monitor
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CNA vs NVD score
- NVD
- 9.8
- CNA · dell
- 8.7
- 1.1 point gap
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
| Vendor | Product | CPE |
|---|---|---|
| cloudfoundry | cf-deployment | cpe:2.3:a:cloudfoundry:cf-deployment |
| cloudfoundry | credhub | cpe:2.3:a:cloudfoundry:credhub |
| cloudfoundry | uaa release | cpe:2.3:a:cloudfoundry:uaa_release |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- cloudfoundry cf-deploymentbefore 7.9.0
- cloudfoundry credhub1.9 and later · before 1.9.10
- cloudfoundry credhub2.1 and later · before 2.1.3
- cloudfoundry uaa releasebefore 64.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (dell). Independent of NVD's CPE analysis and usually ahead of it.
Cloud Foundry cf-deployment
- All and later · before v7.9.0affected
Cloud Foundry CredHub
- 2.1 and later · before 2.1.3affected
- 1.9 and later · before 1.9.10affected
Cloud Foundry UAA Release (OSS)
- All and later · before v64.0affected
Pivotal UAA Release (LTS)
- v60 and later · before v60.2affected
- v64 and later · before v64.1affected
Same product
cloudfoundry: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-31733Starting with diego-release 2.55.0 and up to 2.69.0, and starting with CF Deployment 17.1 and up to 23.2.0, apps are accessible via another 36Monitor
- CVE-2020-5402UAA fails to check the state parameter when authenticating with external IDPs35Monitor
- CVE-2019-11283Password leak in smbdriver logs35Monitor
- CVE-2018-1191Cloud Foundry Garden-runC, versions prior to 1.11.0, contains an information exposure vulnerability.35Monitor
- CVE-2019-11289A forged route service request using an invalid nonce can cause the gorouter to panic and crash34Monitor
- CVE-2019-11277Volume Services is vulnerable to an LDAP injection attack33Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-494 · Download of Code Without Integrity CheckCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Software Integrity AttackCAPEC-184Low
- Malicious Software DownloadCAPEC-185Very High
- Malicious Software UpdateCAPEC-186High
- Malicious Automated Software Update via RedirectionCAPEC-187likelihood: High · High
- Malicious Manual Software UpdateCAPEC-533likelihood: Low · High
- Open-Source Library ManipulationCAPEC-538likelihood: Low · High
- Malicious Automated Software Update via SpoofingCAPEC-657likelihood: High · High
- Adversary in the Browser (AiTB)CAPEC-662likelihood: High · Very High
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.