{"answers":{"affected":"3 open source packages ship an affected version, including keylime. It affects 2 products.","exploited":"There is no known exploitation of CVE-2022-1053 in the wild and no public exploit code.","fix":"Upgrade keylime to 6.4.0 or later.","what":"CVE-2022-1053 is a critical vulnerability in Fedoraproject Fedora, published on 6 May 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-2022-1053 and fix it if it is affected.\n\nWhat it is: CVE-2022-1053 is a critical vulnerability in Fedoraproject Fedora, published on 6 May 2022. 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-2022-1053 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- keylime (PyPI): affected all versions; fixed in 6.4.0\n- keylime (PyPI): affected all versions; fixed in 6.4.0\n- keylime (PyPI): affected all versions; fixed in 6.4.0\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-1053/ (Markdown: https://insights.sbomify.com/CVE-2022-1053/index.md)","id":"CVE-2022-1053","markdown":"https://insights.sbomify.com/CVE-2022-1053/index.md","name":"CVE-2022-1053","record":{"aliases":["GHSA-jf66-3q76-h5p5","GHSA-jf66-3q76-h5p5,","PYSEC-2022-184","openSUSE-SU-2024:12104-1"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Keylime attestation server","requires_auth":"none","summary":"Attackers can bypass TPM attestation by using a software TPM AK after passing EK validation, breaking the chain of trust in Keylime.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"fedora","vendor":"fedoraproject"},{"product":"keylime","vendor":"keylime"}],"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-20","name":"Improper Input Validation"}],"description":"Keylime does not enforce that the agent registrar data is the same when the tenant uses it for validation of the EK and identity quote and the verifier for validating the integrity quote. This allows an attacker to use one AK, EK pair from a real TPM to pass EK validation and give the verifier an AK of a software TPM. A successful attack breaks the entire chain of trust because a not validated AK is used by the verifier. This issue is worse if the validation happens first and then the agent gets added to the verifier because the timing is easier and the verifier does not validate the regcount entry being equal to 1,","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Tenant and Verifier might not use the same registrar data","id":"CVE-2022-1053","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":"fedoraproject:fedora","products":["fedoraproject:fedora"],"type":"security_feature_bypass","year":"2022"},"n_packages":3,"n_references":6,"next":{"headline":"RSVP and Event Management \u003c 2.7.8 - Unauthenticated Entries Export","id":"CVE-2022-1054"},"packages":[{"ecosystem":"PyPI","fixed":["6.4.0"],"introduced":["0"],"last_affected":[],"package":"keylime","purl":null,"source":"GHSA-jf66-3q76-h5p5"},{"ecosystem":"PyPI","fixed":["6.4.0"],"introduced":["0"],"last_affected":[],"package":"keylime","purl":"pkg:pypi/keylime","source":"GHSA-jf66-3q76-h5p5"},{"ecosystem":"PyPI","fixed":["6.4.0"],"introduced":["0"],"last_affected":[],"package":"keylime","purl":"pkg:pypi/keylime","source":"PYSEC-2022-184"}],"prev":{"headline":"Heap Buffer Overflow in iterate_chained_fixups in radareorg/radare2","id":"CVE-2022-1052"},"products":["keylime"],"published":"2022-05-06","related":[{"cvss_score":9.8,"headline":"PHP-CGI OS Command Injection","id":"CVE-2024-4577","kev_date_added":"2024-06-12","published":"2024-06-09"},{"cvss_score":9.8,"headline":"Grafana Authentication Bypass","id":"CVE-2021-39226","kev_date_added":"2022-08-25","published":"2021-10-05"},{"cvss_score":9.8,"headline":"VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow","id":"CVE-2019-5544","kev_date_added":"2021-11-03","published":"2019-12-06"},{"cvss_score":9.6,"headline":"Google Chromium V8 Type Confusion","id":"CVE-2024-4947","kev_date_added":"2024-05-20","published":"2024-05-15"},{"cvss_score":9.6,"headline":"Google Chromium Visuals Use-After-Free","id":"CVE-2024-4671","kev_date_added":"2024-05-13","published":"2024-05-09"},{"cvss_score":9.6,"headline":"Google Chromium Mojo Insufficient Data Validation","id":"CVE-2022-3075","kev_date_added":"2022-09-08","published":"2022-09-26"},{"cvss_score":9.6,"headline":"Google Chromium Indexed DB API Use-After-Free","id":"CVE-2021-30633","kev_date_added":"2021-11-03","published":"2021-10-08"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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-02","vendors":["n/a"]},"summary":"Attackers can bypass TPM attestation by using a software TPM AK after passing EK validation, breaking the chain of trust in Keylime.","url":"https://insights.sbomify.com/CVE-2022-1053/"}