{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-20742 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-20742 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-20742 is a high-severity memory corruption vulnerability in n/a, published on 24 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-20742 and fix it if it is affected.\n\nWhat it is: CVE-2018-20742 is a high-severity memory corruption vulnerability in n/a, published on 24 Jan 2019. 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-2018-20742 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2018-20742/ (Markdown: https://insights.sbomify.com/CVE-2018-20742/index.md)","id":"CVE-2018-20742","markdown":"https://insights.sbomify.com/CVE-2018-20742/index.md","name":"CVE-2018-20742","record":{"aliases":["GHSA-32w7-6rgv-w2xg"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"RISE Opaque library","requires_auth":"none","summary":"Missing boundary checks in ocall_malloc allow arbitrary enclave memory writes, potentially leading to code execution or privilege escalation within the RISE Opaque library.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"opaque","vendor":"ucbrise"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"An issue was discovered in UC Berkeley RISE Opaque before 2018-12-01. There is no boundary check on ocall_malloc. The return value could be a pointer to enclave memory. It could cause an arbitrary enclave memory write.","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 corruption in n/a","id":"CVE-2018-20742","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Denial of service in n/a","id":"CVE-2018-20743"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-20737"},"products":["n/a"],"published":"2019-01-24","related":[],"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":["n/a"]},"summary":"Missing boundary checks in ocall_malloc allow arbitrary enclave memory writes, potentially leading to code execution or privilege escalation within the RISE Opaque library.","url":"https://insights.sbomify.com/CVE-2018-20742/"}