{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-11293 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-11293 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-11293 is a high-severity vulnerability in Cloud Foundry UAA Release, published on 6 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-11293 and fix it if it is affected.\n\nWhat it is: CVE-2019-11293 is a high-severity vulnerability in Cloud Foundry UAA Release, published on 6 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-11293 in the wild and no public exploit code.\n\nAffected product: Cloud Foundry UAA Release. 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-11293/ (Markdown: https://insights.sbomify.com/CVE-2019-11293/index.md)","id":"CVE-2019-11293","markdown":"https://insights.sbomify.com/CVE-2019-11293/index.md","name":"CVE-2019-11293","record":{"aliases":["GHSA-75vm-6gpr-f398"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Cloud Foundry UAA","requires_auth":"low_privilege","summary":"Attackers can read client secrets from logs if debug logging is enabled, exposing credentials to anyone with log access.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"pivotal","cpe":[{"product":"cf-deployment","vendor":"cloudfoundry"},{"product":"user_account_and_authentication","vendor":"cloudfoundry"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"Cloud Foundry UAA Release, versions prior to v74.10.0, when set to logging level DEBUG, logs client_secret credentials when sent as a query parameter. A remote authenticated malicious user could gain access to user credentials via the uaa.log file if authentication is provided via query parameters.","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 logs all query parameters with debug logging level","id":"CVE-2019-11293","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"CAPI leaks service broker URLs and GUIDs to space developers","id":"CVE-2019-11294"},"packages":[],"prev":{"headline":"Pivotal Ops Manager logs query parameters in tomcat access file","id":"CVE-2019-11292"},"products":["UAA Release"],"published":"2019-12-06","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":"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"},{"cvss_score":8.7,"headline":"Java Projects using HTTP to fetch dependencies","id":"CVE-2019-3801","kev_date_added":null,"published":"2019-04-25"}],"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 read client secrets from logs if debug logging is enabled, exposing credentials to anyone with log access.","url":"https://insights.sbomify.com/CVE-2019-11293/"}