{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-22552 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-22552 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-22552 is a medium-severity vulnerability in Google LLC Asylo, published on 2 Aug 2021. 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-2021-22552 and fix it if it is affected.\n\nWhat it is: CVE-2021-22552 is a medium-severity vulnerability in Google LLC Asylo, published on 2 Aug 2021. 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-2021-22552 in the wild and no public exploit code.\n\nAffected product: Google LLC Asylo. 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-22552/ (Markdown: https://insights.sbomify.com/CVE-2021-22552/index.md)","id":"CVE-2021-22552","markdown":"https://insights.sbomify.com/CVE-2021-22552/index.md","name":"CVE-2021-22552","record":{"aliases":["GHSA-wjwj-7rpq-5gg8"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Asylo secure enclave library","requires_auth":"low_privilege","summary":"An attacker can read memory from within the secure enclave by bypassing syscall validation, exposing sensitive data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Google","cpe":[{"product":"asylo","vendor":"google"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"},{"id":"CWE-126","name":"Buffer Over-read"}],"description":"An untrusted memory read vulnerability in Asylo versions up to 0.6.1 allows an untrusted attacker to pass a syscall number in MessageReader that is then used by sysno() and can bypass validation. This can allow the attacker to read memory from within the secure enclave. We recommend updating to Asylo 0.6.3 or past https://github.com/google/asylo/commit/90d7619e9dd99bcdb6cd28c7649d741d254d9a1a","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":"Memory overread secure enclave in Asylo 0.6.2","id":"CVE-2021-22552","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Heap Memory exhaustion in Gerrit","id":"CVE-2021-22553"},"packages":[],"prev":{"headline":"Enclave memory overwrite/overread vulnerability in Asylo UntrustedCacheMalloc::GetBuffer","id":"CVE-2021-22550"},"products":["Asylo"],"published":"2021-08-02","related":[{"cvss_score":6.5,"headline":"Arbitrary enclave memory overread vulnerability in Asylo TrustedPrimitives::UntrustedCall","id":"CVE-2021-22548","kev_date_added":null,"published":"2021-06-08"},{"cvss_score":6.5,"headline":"Arbitrary enclave memory overwrite vulnerability in Asylo TrustedPrimitives::UntrustedCall","id":"CVE-2021-22549","kev_date_added":null,"published":"2021-06-08"},{"cvss_score":6.5,"headline":"Enclave memory overwrite/overread vulnerability in Asylo UntrustedCacheMalloc::GetBuffer","id":"CVE-2021-22550","kev_date_added":null,"published":"2021-06-08"},{"cvss_score":6.4,"headline":"Arbitrary trusted memory overwrite vulnerability in Asylo","id":"CVE-2020-8904","kev_date_added":null,"published":"2020-08-12"},{"cvss_score":5.3,"headline":"Memory corruption in Asylo","id":"CVE-2020-8935","kev_date_added":null,"published":"2020-12-15"},{"cvss_score":5.3,"headline":"Arbitrary enclave memory overwrite vulnerability in ECall ecall_restore","id":"CVE-2020-8936","kev_date_added":null,"published":"2020-12-15"}],"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-09-17","vendors":["Google LLC"]},"summary":"An attacker can read memory from within the secure enclave by bypassing syscall validation, exposing sensitive data.","url":"https://insights.sbomify.com/CVE-2021-22552/"}