{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-8941 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-8941 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-8941 is a medium-severity memory corruption vulnerability in Google LLC Asylo, published on 15 Dec 2020. 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-2020-8941 and fix it if it is affected.\n\nWhat it is: CVE-2020-8941 is a medium-severity memory corruption vulnerability in Google LLC Asylo, published on 15 Dec 2020. 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-2020-8941 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-2020-8941/ (Markdown: https://insights.sbomify.com/CVE-2020-8941/index.md)","id":"CVE-2020-8941","markdown":"https://insights.sbomify.com/CVE-2020-8941/index.md","name":"CVE-2020-8941","record":{"aliases":["GHSA-j42c-839r-f79f"],"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 outside intended buffers, including secure enclave memory, by exploiting an unchecked buffer overrun in Asylo.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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-120","name":"Buffer Copy without Checking Size of Input"}],"description":"An arbitrary memory read vulnerability in Asylo versions up to 0.6.0 allows an untrusted attacker to make a call to enc_untrusted_inet_pton using an attacker controlled klinux_addr_buffer parameter. The parameter size is unchecked allowing the attacker to read memory locations outside of the intended buffer size including memory addresses within the secure enclave. We recommend upgrading past commit 8fed5e334131abaf9c5e17307642fbf6ce4a57ec","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":"Unchecked buffer overrun in enc_untrusted_inet_pton","id":"CVE-2020-8941","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Unchecked buffer overrun in enc_untrusted_read","id":"CVE-2020-8942"},"packages":[],"prev":{"headline":"Unchecked buffer overrun in enc_untrusted_recvmsg","id":"CVE-2020-8940"},"products":["Asylo"],"published":"2020-12-15","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 overread secure enclave in Asylo 0.6.2","id":"CVE-2021-22552","kev_date_added":null,"published":"2021-08-02"},{"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-08-04","vendors":["Google LLC"]},"summary":"An attacker can read memory outside intended buffers, including secure enclave memory, by exploiting an unchecked buffer overrun in Asylo.","url":"https://insights.sbomify.com/CVE-2020-8941/"}