{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-8905 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-8905 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-8905 is a low-severity vulnerability in Google LLC Asylo, published on 12 Aug 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-8905 and fix it if it is affected.\n\nWhat it is: CVE-2020-8905 is a low-severity vulnerability in Google LLC Asylo, published on 12 Aug 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-8905 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-8905/ (Markdown: https://insights.sbomify.com/CVE-2020-8905/index.md)","id":"CVE-2020-8905","markdown":"https://insights.sbomify.com/CVE-2020-8905/index.md","name":"CVE-2020-8905","record":{"aliases":["GHSA-xr5f-j5gc-qw6j"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Asylo library","requires_auth":"low_privilege","summary":"An attacker can read trusted memory data by exploiting a buffer length validation flaw in the Asylo library's network receive function.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Google","cpe":[{"product":"asylo","vendor":"google"}],"cvss":{"score":2.8,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-120","name":"Buffer Copy without Checking Size of Input"}],"description":"A buffer length validation vulnerability in Asylo versions prior to 0.6.0 allows an attacker to read data they should not have access to. The 'enc_untrusted_recvfrom' function generates a return value which is deserialized by 'MessageReader', and copied into three different 'extents'. The length of the third 'extents' is controlled by the outside world, and not verified on copy, allowing the attacker to force Asylo to copy trusted memory data into an untrusted buffer of significantly small length.. We recommend updating Asylo to version 0.6.0 or later.","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":"Confidential Information Disclosure vulnerability in Asylo","id":"CVE-2020-8905","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Priviged Escalation in Google Cloud Platform's Guest-OSLogin","id":"CVE-2020-8907"},"packages":[],"prev":{"headline":"Arbitrary trusted memory overwrite vulnerability in Asylo","id":"CVE-2020-8904"},"products":["Asylo"],"published":"2020-08-12","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-09-17","vendors":["Google LLC"]},"summary":"An attacker can read trusted memory data by exploiting a buffer length validation flaw in the Asylo library's network receive function.","url":"https://insights.sbomify.com/CVE-2020-8905/"}