{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-8904 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-8904 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-8904 is a medium-severity memory corruption 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-8904 and fix it if it is affected.\n\nWhat it is: CVE-2020-8904 is a medium-severity memory corruption 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-8904 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-8904/ (Markdown: https://insights.sbomify.com/CVE-2020-8904/index.md)","id":"CVE-2020-8904","markdown":"https://insights.sbomify.com/CVE-2020-8904/index.md","name":"CVE-2020-8904","record":{"aliases":["GHSA-pc43-829f-g5gr"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Asylo enclave library","requires_auth":"low_privilege","summary":"Attackers can overwrite arbitrary trusted memory in Asylo enclaves due to missing pointer validation, potentially leading to code execution or privilege escalation.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Google","cpe":[{"product":"asylo","vendor":"google"}],"cvss":{"score":6.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:H","version":"3.1"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"},{"id":"CWE-823","name":"Use of Out-of-range Pointer Offset"}],"description":"An arbitrary memory overwrite vulnerability in the trusted memory of Asylo exists in versions prior to 0.6.0. As the ecall_restore function fails to validate the range of the output_len pointer, an attacker can manipulate the tmp_output_len value and write to an arbitrary location in the trusted (enclave) memory. 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":"Arbitrary trusted memory overwrite vulnerability in Asylo","id":"CVE-2020-8904","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":"Confidential Information Disclosure vulnerability in Asylo","id":"CVE-2020-8905"},"packages":[],"prev":{"headline":"Priviged Escalation in Google Cloud Platform's Guest-OSLogin","id":"CVE-2020-8903"},"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":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-16","vendors":["Google LLC"]},"summary":"Attackers can overwrite arbitrary trusted memory in Asylo enclaves due to missing pointer validation, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2020-8904/"}