{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-11292 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-11292 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-11292 is a high-severity vulnerability in Pivotal Ops Manager, published on 8 Jan 2020. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-11292 and fix it if it is affected.\n\nWhat it is: CVE-2019-11292 is a high-severity vulnerability in Pivotal Ops Manager, published on 8 Jan 2020. 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-11292 in the wild and no public exploit code.\n\nAffected product: Pivotal Ops Manager. 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-11292/ (Markdown: https://insights.sbomify.com/CVE-2019-11292/index.md)","id":"CVE-2019-11292","markdown":"https://insights.sbomify.com/CVE-2019-11292/index.md","name":"CVE-2019-11292","record":{"aliases":["GHSA-qxj4-46g2-7rv9"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Pivotal Ops Manager","requires_auth":"low_privilege","summary":"Attackers with access to Tomcat logs can read sensitive authentication credentials if they are passed via query parameters.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"pivotal","cpe":[{"product":"operations_manager","vendor":"pivotal_software"}],"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":"Pivotal Ops Manager, versions 2.4.x prior to 2.4.27, 2.5.x prior to 2.5.24, 2.6.x prior to 2.6.16, and 2.7.x prior to 2.7.5, logs all query parameters to tomcat’s access file. If the query parameters are used to provide authentication, ie. credentials, then they will be logged as well.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Pivotal Ops Manager logs query parameters in tomcat access file","id":"CVE-2019-11292","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":"UAA logs all query parameters with debug logging level","id":"CVE-2019-11293"},"packages":[],"prev":{"headline":"RabbitMQ XSS attack via federation and shovel endpoints","id":"CVE-2019-11291"},"products":["Pivotal Ops Manager"],"published":"2020-01-08","related":[{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2016-0883","kev_date_added":null,"published":"2016-09-18"},{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2016-0897","kev_date_added":null,"published":"2016-09-18"},{"cvss_score":9,"headline":"Pivotal Operations Manager gives all users heightened privileges","id":"CVE-2018-15762","kev_date_added":null,"published":"2018-11-02"},{"cvss_score":7.9,"headline":"Pivotal Operations Manager UAA config - temp Ram Disk","id":"CVE-2018-11081","kev_date_added":null,"published":"2018-10-05"},{"cvss_score":7.2,"headline":"Reflected XSS in Pivotal Operations Manager","id":"CVE-2019-3776","kev_date_added":null,"published":"2019-03-07"},{"cvss_score":6.5,"headline":"Other in Operations Manager","id":"CVE-2018-11046","kev_date_added":null,"published":"2018-06-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":["Pivotal"]},"summary":"Attackers with access to Tomcat logs can read sensitive authentication credentials if they are passed via query parameters.","url":"https://insights.sbomify.com/CVE-2019-11292/"}