{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-43310 exists.","fix":"No fix has been published for CVE-2021-43310 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-43310 is a critical authentication bypass vulnerability in keylime, published on 21 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-43310 and fix it if it is affected.\n\nWhat it is: CVE-2021-43310 is a critical authentication bypass vulnerability in keylime, published on 21 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-43310 exists.\n\nAffected product: keylime. 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-2021-43310/ (Markdown: https://insights.sbomify.com/CVE-2021-43310/index.md)","id":"CVE-2021-43310","markdown":"https://insights.sbomify.com/CVE-2021-43310/index.md","name":"CVE-2021-43310","record":{"aliases":["GHSA-2m39-75g9-ff5r"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Keylime agent","requires_auth":"none","summary":"An attacker can reset agent keys via crafted requests, leading to remote code execution in Keylime deployments.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"fedora","cpe":[{"product":"keylime","vendor":"keylime"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-290","name":"Authentication Bypass by Spoofing"}],"description":"A vulnerability in Keylime before 6.3.0 allows an attacker to craft a request to the agent that resets the U and V keys as if the agent were being re-added to a verifier. This could lead to a remote code execution.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Auth bypass in keylime","id":"CVE-2021-43310","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in upx","id":"CVE-2021-43311"},"packages":[],"prev":{"headline":"ReDoS in uri-template-lite URI.expand function","id":"CVE-2021-43309"},"products":["keylime"],"published":"2022-09-21","related":[{"cvss_score":9.4,"headline":"Keylime Missing Authentication for Critical Function and Improper Authentication","id":"CVE-2026-1709","kev_date_added":null,"published":"2026-02-06"},{"cvss_score":7.5,"headline":"Information disclosure in keylime","id":"CVE-2022-23948","kev_date_added":null,"published":"2022-09-21"},{"cvss_score":7.5,"headline":"Other in keylime","id":"CVE-2022-23949","kev_date_added":null,"published":"2022-09-21"},{"cvss_score":7.5,"headline":"Denial of service in keylime","id":"CVE-2022-23950","kev_date_added":null,"published":"2022-09-21"},{"cvss_score":7.5,"headline":"Information disclosure in keylime","id":"CVE-2022-23952","kev_date_added":null,"published":"2022-09-21"},{"cvss_score":5.5,"headline":"Denial of service in keylime","id":"CVE-2022-23951","kev_date_added":null,"published":"2022-09-21"}],"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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-05-27","vendors":["n/a"]},"summary":"An attacker can reset agent keys via crafted requests, leading to remote code execution in Keylime deployments.","url":"https://insights.sbomify.com/CVE-2021-43310/"}