{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-37397 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-37397 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-37397 is a high-severity authentication bypass vulnerability in YugaByte, Inc. Yugabyte DB, published on 12 Aug 2022. 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-2022-37397 and fix it if it is affected.\n\nWhat it is: CVE-2022-37397 is a high-severity authentication bypass vulnerability in YugaByte, Inc. Yugabyte DB, published on 12 Aug 2022. 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-2022-37397 in the wild and no public exploit code.\n\nAffected product: YugaByte, Inc. Yugabyte DB. 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-2022-37397/ (Markdown: https://insights.sbomify.com/CVE-2022-37397/index.md)","id":"CVE-2022-37397","markdown":"https://insights.sbomify.com/CVE-2022-37397/index.md","name":"CVE-2022-37397","record":{"aliases":["GHSA-3r4j-8whf-548p"],"analysis":{"component_type":"database","fix_type":"configuration_change","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"YugabyteDB database","requires_auth":"none","summary":"Attackers can bypass authentication in YugabyteDB by using an empty password when anonymous LDAP binding is enabled.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Yugabyte","cpe":[{"product":"yugabytedb","vendor":"yugabyte"}],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"},{"id":"CWE-16","name":null}],"description":"An issue was discovered in the YugabyteDB 2.6.1 when using LDAP-based authentication in YCQL with Microsoft’s Active Directory. When anonymous or unauthenticated LDAP binding is enabled, it allows bypass of authentication with an empty password.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"The software is vulnerable when using LDAP-based authentication in YCQL with Microsoft’s Active Directory","id":"CVE-2022-37397","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"A stack-based buffer overflow vulnerability was found on ADM","id":"CVE-2022-37398"},"packages":[],"prev":{"headline":"Security feature bypass in Rider","id":"CVE-2022-37396"},"products":["Yugabyte DB"],"published":"2022-08-12","related":[{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2024-41435","kev_date_added":null,"published":"2024-09-03"},{"cvss_score":7.2,"headline":"Remote Code Execution","id":"CVE-2023-0575","kev_date_added":null,"published":"2023-02-09"},{"cvss_score":6.5,"headline":"Log Injection","id":"CVE-2023-6002","kev_date_added":null,"published":"2023-11-07"},{"cvss_score":6.5,"headline":"Set Logging Level Without Authentication","id":"CVE-2023-4640","kev_date_added":null,"published":"2023-08-30"},{"cvss_score":5.3,"headline":"Prometheus Metrics Accessible Pre-Authentication","id":"CVE-2023-6001","kev_date_added":null,"published":"2023-11-07"}],"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-03","vendors":["YugaByte, Inc."]},"summary":"Attackers can bypass authentication in YugabyteDB by using an empty password when anonymous LDAP binding is enabled.","url":"https://insights.sbomify.com/CVE-2022-37397/"}