{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-2203 exists.","fix":"No fix has been published for CVE-2016-2203 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-2203 is a high-severity vulnerability in n/a, published on 22 Apr 2016. 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-2016-2203 and fix it if it is affected.\n\nWhat it is: CVE-2016-2203 is a high-severity vulnerability in n/a, published on 22 Apr 2016. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-2203 exists.\n\nAffected product: n/a. 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-2016-2203/ (Markdown: https://insights.sbomify.com/CVE-2016-2203/index.md)","id":"CVE-2016-2203","markdown":"https://insights.sbomify.com/CVE-2016-2203/index.md","name":"CVE-2016-2203","record":{"aliases":["GHSA-w4px-29jm-36xf"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Symantec Messaging Gateway","requires_auth":"low_privilege","summary":"Local users with read privileges can discover encrypted Active Directory passwords in the Symantec Messaging Gateway management console.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"symantec","cpe":[{"product":"messaging_gateway","vendor":"symantec"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-255","name":null}],"description":"The management console on Symantec Messaging Gateway (SMG) Appliance devices before 10.6.1 allows local users to discover an encrypted AD password by leveraging certain read privileges.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2015-12-17","github_poc":0,"max_poc_stars":null,"metasploit":1,"nuclei":0,"refs":[{"date":"2015-12-17","kind":"metasploit","ref":"auxiliary/scanner/http/symantec_brightmail_ldapcreds","stars":null,"title":"Symantec Messaging Gateway 10 Exposure of Stored AD Password Vulnerability"},{"date":"2016-04-21","kind":"exploitdb","ref":"39715","stars":null,"title":"Symantec Brightmail 10.6.0-7 - LDAP Credentials Disclosure (Metasploit)"}],"tier":"weaponised"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2016-2203","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2016"},"n_packages":0,"n_references":5,"next":{"headline":"Command injection in n/a","id":"CVE-2016-2204"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2016-2202"},"products":["n/a"],"published":"2016-04-22","related":[{"cvss_score":10,"headline":"Code injection in Messaging Gateway","id":"CVE-2017-6326","kev_date_added":null,"published":"2017-06-26"},{"cvss_score":9.8,"headline":"Auth bypass in Symantec Messaging Gateway","id":"CVE-2018-12242","kev_date_added":null,"published":"2018-09-19"},{"cvss_score":8.8,"headline":"XML external entity in Symantec Messaging Gateway","id":"CVE-2018-12243","kev_date_added":null,"published":"2018-09-19"},{"cvss_score":8.2,"headline":"Command injection in n/a","id":"CVE-2016-2204","kev_date_added":null,"published":"2016-04-22"},{"cvss_score":7.9,"headline":"Hardcoded credentials in n/a","id":"CVE-2012-3579","kev_date_added":null,"published":"2012-08-29"},{"cvss_score":7.7,"headline":"Missing authorization in n/a","id":"CVE-2012-3580","kev_date_added":null,"published":"2012-08-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)"},{"class":"attribution","licence":"BSD-3-Clause","name":"Metasploit"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Local users with read privileges can discover encrypted Active Directory passwords in the Symantec Messaging Gateway management console.","url":"https://insights.sbomify.com/CVE-2016-2203/"}