{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-6144 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-6144 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-6144 is a high-severity authentication bypass vulnerability in n/a, published on 5 Aug 2016. 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-6144 and fix it if it is affected.\n\nWhat it is: CVE-2016-6144 is a high-severity authentication bypass vulnerability in n/a, published on 5 Aug 2016. 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-6144 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-6144/ (Markdown: https://insights.sbomify.com/CVE-2016-6144/index.md)","id":"CVE-2016-6144","markdown":"https://insights.sbomify.com/CVE-2016-6144/index.md","name":"CVE-2016-6144","record":{"aliases":["GHSA-pj38-v8h9-33p3"],"analysis":{"component_type":"database","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"SAP HANA database","requires_auth":"none","summary":"Remote attackers can bypass authentication for the SYSTEM user via brute force if password locking is disabled, leading to account takeover.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"hana","vendor":"sap"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"The SQL interface in SAP HANA before Revision 102 does not limit the number of login attempts for the SYSTEM user when the password_lock_for_system_user is not supported or is configured as \"False,\" which makes it easier for remote attackers to bypass authentication via a brute force attack, aka SAP Security Note 2216869.","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":"Auth bypass in n/a","id":"CVE-2016-6144","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2016"},"n_packages":0,"n_references":5,"next":{"headline":"Information disclosure in n/a","id":"CVE-2016-6145"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2016-6143"},"products":["n/a"],"published":"2016-08-05","related":[{"cvss_score":10,"headline":"Auth bypass in n/a","id":"CVE-2015-7828","kev_date_added":null,"published":"2015-11-10"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2016-6143","kev_date_added":null,"published":"2017-04-13"},{"cvss_score":9.8,"headline":"Weak cryptography in n/a","id":"CVE-2016-6150","kev_date_added":null,"published":"2016-08-05"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2016-1928","kev_date_added":null,"published":"2016-01-20"},{"cvss_score":9.3,"headline":"Denial of service in n/a","id":"CVE-2016-1929","kev_date_added":null,"published":"2016-01-20"},{"cvss_score":7.7,"headline":"Auth bypass in SAP HANA","id":"CVE-2021-21484","kev_date_added":null,"published":"2021-03-09"}],"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":"Remote attackers can bypass authentication for the SYSTEM user via brute force if password locking is disabled, leading to account takeover.","url":"https://insights.sbomify.com/CVE-2016-6144/"}