{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2019-3801 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-3801 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-3801 is a high-severity vulnerability in Cloud Foundry CredHub, published on 25 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-3801 and fix it if it is affected.\n\nWhat it is: CVE-2019-3801 is a high-severity vulnerability in Cloud Foundry CredHub, published on 25 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-3801 in the wild and no public exploit code.\n\nAffected product: Cloud Foundry CredHub. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2019-3801/ (Markdown: https://insights.sbomify.com/CVE-2019-3801/index.md)","id":"CVE-2019-3801","markdown":"https://insights.sbomify.com/CVE-2019-3801/index.md","name":"CVE-2019-3801","record":{"aliases":["GHSA-4w8g-vwqf-w48w"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Cloud Foundry deployment","requires_auth":"none","summary":"Attackers can hijack DNS to inject malicious code into Cloud Foundry components by exploiting insecure HTTP dependency fetching during builds.","user_interaction":"not_required","vuln_class":"supply_chain"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"dell","cpe":[{"product":"cf-deployment","vendor":"cloudfoundry"},{"product":"credhub","vendor":"cloudfoundry"},{"product":"uaa_release","vendor":"cloudfoundry"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-319","name":"Cleartext Transmission of Sensitive Information"},{"id":"CWE-494","name":"Download of Code Without Integrity Check"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Java Projects using HTTP to fetch dependencies","id":"CVE-2019-3801","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"supply_chain","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Additional information exposure with Spring Data JPA example matcher","id":"CVE-2019-3802"},"packages":[],"prev":{"headline":"CF CLI writes the client id and secret to config file","id":"CVE-2019-3800"},"products":["CredHub","UAA Release (LTS)","UAA Release (OSS)","cf-deployment"],"published":"2019-04-25","related":[{"cvss_score":9.1,"headline":"Auth bypass in Cloud Foundry Diego and CF Deployment","id":"CVE-2022-31733","kev_date_added":null,"published":"2023-02-03"},{"cvss_score":8.8,"headline":"UAA fails to check the state parameter when authenticating with external IDPs","id":"CVE-2020-5402","kev_date_added":null,"published":"2020-02-27"},{"cvss_score":8.8,"headline":"UAA logs all query parameters with debug logging level","id":"CVE-2019-11293","kev_date_added":null,"published":"2019-12-06"},{"cvss_score":8.8,"headline":"Cloud Foundry UAA logs query parameters in tomcat access file","id":"CVE-2019-11290","kev_date_added":null,"published":"2019-11-25"},{"cvss_score":8.8,"headline":"Password leak in smbdriver logs","id":"CVE-2019-11283","kev_date_added":null,"published":"2019-10-23"},{"cvss_score":8.8,"headline":"Information disclosure in Garden-runC","id":"CVE-2018-1191","kev_date_added":null,"published":"2018-03-29"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["Cloud Foundry","Pivotal"]},"summary":"Attackers can hijack DNS to inject malicious code into Cloud Foundry components by exploiting insecure HTTP dependency fetching during builds.","url":"https://insights.sbomify.com/CVE-2019-3801/"}