{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2017-4966 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2017-4966 is a high-severity vulnerability in Broadcom Rabbitmq Server, published on 13 Jun 2017. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-4966 and fix it if it is affected.\n\nWhat it is: CVE-2017-4966 is a high-severity vulnerability in Broadcom Rabbitmq Server, published on 13 Jun 2017. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-4966 in the wild and no public exploit code.\n\nAffected product: Broadcom Rabbitmq Server. 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-2017-4966/ (Markdown: https://insights.sbomify.com/CVE-2017-4966/index.md)","id":"CVE-2017-4966","markdown":"https://insights.sbomify.com/CVE-2017-4966/index.md","name":"CVE-2017-4966","record":{"aliases":["DEBIAN-CVE-2017-4966","GHSA-cp6g-c34h-69q7","UBUNTU-CVE-2017-4966","USN-6265-1"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"RabbitMQ management UI","requires_auth":"low_privilege","summary":"Attackers can retrieve stored user credentials from browser local storage in RabbitMQ management UI, potentially leading to account takeover.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"dell","cpe":[{"product":"rabbitmq_server","vendor":"broadcom"},{"product":"debian_linux","vendor":"debian"},{"product":"rabbitmq","vendor":"pivotal_software"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"An issue was discovered in these Pivotal RabbitMQ versions: all 3.4.x versions, all 3.5.x versions, and 3.6.x versions prior to 3.6.9; and these RabbitMQ for PCF versions: all 1.5.x versions, 1.6.x versions prior to 1.6.18, and 1.7.x versions prior to 1.7.15. RabbitMQ management UI stores signed-in user credentials in a browser's local storage without expiration, making it possible to retrieve them using a chained attack.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Information disclosure in Pivotal RabbitMQ","id":"CVE-2017-4966","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"broadcom:rabbitmq_server","products":["broadcom:rabbitmq_server","debian:debian_linux"],"type":"information_disclosure","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in Pivotal RabbitMQ","id":"CVE-2017-4967"},"packages":[],"prev":{"headline":"Cross-site scripting in Pivotal RabbitMQ","id":"CVE-2017-4965"},"products":["Pivotal RabbitMQ"],"published":"2017-06-13","related":[{"cvss_score":9.8,"headline":"Auth bypass in Pivotal RabbitMQ 3.x before 3.5.8 and 3.6.x before 3.6.6; RabbitMQ for PCF 1.5.x before 1.5.20, 1.6.x before 1.6.12 and 1.7.x before 1.7.7","id":"CVE-2016-9877","kev_date_added":null,"published":"2016-12-29"},{"cvss_score":9.2,"headline":"RabbitMQ: OAuth2 silent verify_none fallback for JWKS fetch","id":"CVE-2026-67404","kev_date_added":null,"published":"2026-09-23"},{"cvss_score":9.1,"headline":"RabbitMQ: Trust-store whitelist by Issuer+Serial only","id":"CVE-2026-67231","kev_date_added":null,"published":"2026-09-23"},{"cvss_score":8.7,"headline":"Information disclosure in rabbitmq-server","id":"CVE-2026-57219","kev_date_added":null,"published":"2026-07-10"},{"cvss_score":8.2,"headline":"RabbitMQ: Plaintext username:password stored in an insecure cookie after successful POST /login","id":"CVE-2026-67236","kev_date_added":null,"published":"2026-09-25"},{"cvss_score":8.2,"headline":"RabbitMQ: JWKS Fetch Ignores HTTP Response Status Code - Signing Key Destruction Causes Authentication DoS","id":"CVE-2026-67409","kev_date_added":null,"published":"2026-09-25"},{"cvss_score":8.2,"headline":"RabbitMQ: OAuth2 Client Secret Exposed via Unauthenticated JavaScript Endpoint","id":"CVE-2026-67410","kev_date_added":null,"published":"2026-09-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-08-05","vendors":["n/a"]},"summary":"Attackers can retrieve stored user credentials from browser local storage in RabbitMQ management UI, potentially leading to account takeover.","url":"https://insights.sbomify.com/CVE-2017-4966/"}