{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-9433 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-9433 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-9433 is a critical vulnerability in n/a, published on 27 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-9433 and fix it if it is affected.\n\nWhat it is: CVE-2020-9433 is a critical vulnerability in n/a, published on 27 Feb 2020. 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-2020-9433 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-2020-9433/ (Markdown: https://insights.sbomify.com/CVE-2020-9433/index.md)","id":"CVE-2020-9433","markdown":"https://insights.sbomify.com/CVE-2020-9433/index.md","name":"CVE-2020-9433","record":{"aliases":["GHSA-4mrg-rj5w-4j8j"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Lua OpenSSL library","requires_auth":"none","summary":"An attacker can bypass X.509 certificate validation in lua-openssl due to incorrect boolean handling, potentially allowing man-in-the-middle attacks.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"lua-openssl","vendor":"lua-openssl_project"}],"cvss":{"score":9.1,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"openssl_x509_check_email in lua-openssl 0.7.7-1 mishandles X.509 certificate validation because it uses lua_pushboolean for certain non-boolean return values.","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":"Security feature bypass in n/a","id":"CVE-2020-9433","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2020-9434"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2020-9432"},"products":["n/a"],"published":"2020-02-27","related":[{"cvss_score":9.1,"headline":"Security feature bypass in n/a","id":"CVE-2020-9432","kev_date_added":null,"published":"2020-02-27"},{"cvss_score":9.1,"headline":"Security feature bypass in n/a","id":"CVE-2020-9434","kev_date_added":null,"published":"2020-02-27"}],"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-04","vendors":["n/a"]},"summary":"An attacker can bypass X.509 certificate validation in lua-openssl due to incorrect boolean handling, potentially allowing man-in-the-middle attacks.","url":"https://insights.sbomify.com/CVE-2020-9433/"}