{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-6497 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-6497 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-6497 is a high-severity vulnerability in n/a, published on 18 Jan 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-6497 and fix it if it is affected.\n\nWhat it is: CVE-2016-6497 is a high-severity vulnerability in n/a, published on 18 Jan 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2016-6497 in the wild and no public exploit code.\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-6497/ (Markdown: https://insights.sbomify.com/CVE-2016-6497/index.md)","id":"CVE-2016-6497","markdown":"https://insights.sbomify.com/CVE-2016-6497/index.md","name":"CVE-2016-6497","record":{"aliases":["GHSA-2pwj-47v7-pcxg"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Groovy LDAP API","requires_auth":"none","summary":"Attackers can poison LDAP entries by exploiting a configuration flaw in the Groovy LDAP API search methods.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hpe","cpe":[{"product":"groovy_ldap","vendor":"apache"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-254","name":null}],"description":"main/java/org/apache/directory/groovyldap/LDAP.java in the Groovy LDAP API in Apache allows attackers to conduct LDAP entry poisoning attacks by leveraging setting returnObjFlag to true for all search methods.","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":"Other in n/a","id":"CVE-2016-6497","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2016"},"n_packages":0,"n_references":5,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2016-6498"},"packages":[],"prev":{"headline":"Deserialization in n/a","id":"CVE-2016-6496"},"products":["n/a"],"published":"2017-01-18","related":[],"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-06","vendors":["n/a"]},"summary":"Attackers can poison LDAP entries by exploiting a configuration flaw in the Groovy LDAP API search methods.","url":"https://insights.sbomify.com/CVE-2016-6497/"}