{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-3787 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-3787 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-3787 is a high-severity vulnerability in Cloud Foundry UAA Release (OSS), published on 19 Jun 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-3787 and fix it if it is affected.\n\nWhat it is: CVE-2019-3787 is a high-severity vulnerability in Cloud Foundry UAA Release (OSS), published on 19 Jun 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-3787 in the wild and no public exploit code.\n\nAffected product: Cloud Foundry UAA Release (OSS). 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-3787/ (Markdown: https://insights.sbomify.com/CVE-2019-3787/index.md)","id":"CVE-2019-3787","markdown":"https://insights.sbomify.com/CVE-2019-3787/index.md","name":"CVE-2019-3787","record":{"aliases":["GHSA-7rf4-2hjj-cg48"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Cloud Foundry UAA","requires_auth":"none","summary":"Attackers can hijack user accounts by exploiting default email domain fallbacks that direct password recovery emails to attacker-controlled domains.","user_interaction":"required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"dell","cpe":[{"product":"cloud_foundry_uaa-release","vendor":"pivotal_software"}],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-640","name":"Weak Password Recovery Mechanism for Forgotten Password"},{"id":"CWE-840","name":null}],"description":"Cloud Foundry UAA, versions prior to 73.0.0, falls back to appending “unknown.org” to a user's email address when one is not provided and the user name does not contain an @ character. This domain is held by a private company, which leads to attack vectors including password recovery emails sent to a potentially fraudulent address. This would allow the attacker to gain complete control of the user's account.","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":"UAA defaults email address to an insecure domain","id":"CVE-2019-3787","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"UAA redirect-uri allows wildcard in the subdomain","id":"CVE-2019-3788"},"packages":[],"prev":{"headline":"BBR could run arbitrary scripts on deployment VMs","id":"CVE-2019-3786"},"products":["UAA Release (OSS)"],"published":"2019-06-19","related":[{"cvss_score":6.5,"headline":"UAA SQL Identity Zone Vulnerability","id":"CVE-2019-11268","kev_date_added":null,"published":"2019-07-11"},{"cvss_score":4.2,"headline":"UAA can issue tokens across identity providers if users with matching usernames exist","id":"CVE-2018-15754","kev_date_added":null,"published":"2018-12-13"}],"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-16","vendors":["Cloud Foundry"]},"summary":"Attackers can hijack user accounts by exploiting default email domain fallbacks that direct password recovery emails to attacker-controlled domains.","url":"https://insights.sbomify.com/CVE-2019-3787/"}