{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-4640 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-4640 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-4640 is a medium-severity missing authorization vulnerability in YugabyteDB Anywhere, published on 30 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-4640 and fix it if it is affected.\n\nWhat it is: CVE-2023-4640 is a medium-severity missing authorization vulnerability in YugabyteDB Anywhere, published on 30 Aug 2023. 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-2023-4640 in the wild and no public exploit code.\n\nAffected product: YugabyteDB Anywhere. 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-2023-4640/ (Markdown: https://insights.sbomify.com/CVE-2023-4640/index.md)","id":"CVE-2023-4640","markdown":"https://insights.sbomify.com/CVE-2023-4640/index.md","name":"CVE-2023-4640","record":{"aliases":["GHSA-jqrr-cj4q-x8m4"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"YugabyteDB Anywhere","requires_auth":"none","summary":"Unauthenticated attackers can modify logging levels in YugabyteDB Anywhere due to missing authorization checks in the controller.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Yugabyte","cpe":[{"product":"yugabytedb","vendor":"yugabyte"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"The controller responsible for setting the logging level does not include any authorization\nchecks to ensure the user is authenticated. This can be seen by noting that it extends\nController rather than AuthenticatedController and includes no further checks. This issue affects YugabyteDB Anywhere: from 2.0.0 through 2.17.3","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":"Set Logging Level Without Authentication","id":"CVE-2023-4640","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Shadow-utils: possible password leak during passwd(1) change","id":"CVE-2023-4641"},"packages":[],"prev":{"headline":"Undertow: cookie smuggling/spoofing","id":"CVE-2023-4639"},"products":["Anywhere"],"published":"2023-08-30","related":[{"cvss_score":8.3,"headline":"The software is vulnerable when using LDAP-based authentication in YCQL with Microsoft’s Active Directory","id":"CVE-2022-37397","kev_date_added":null,"published":"2022-08-12"},{"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":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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-10-01","vendors":["YugabyteDB"]},"summary":"Unauthenticated attackers can modify logging levels in YugabyteDB Anywhere due to missing authorization checks in the controller.","url":"https://insights.sbomify.com/CVE-2023-4640/"}