# CVE-2018-20742: Memory corruption in n/a

> Missing boundary checks in ocall_malloc allow arbitrary enclave memory writes, potentially leading to code execution or privilege escalation within the RISE Opaque library.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jan 2019
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-32w7-6rgv-w2xg

## What is CVE-2018-20742?

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.

### Official 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.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2018-20742?

It affects 1 product.


Products: Ucbrise Opaque.

## How do I fix CVE-2018-20742?

No fix has been published for CVE-2018-20742 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-20742 being exploited?

There is no known exploitation of CVE-2018-20742 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-20742 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2018-20742 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-20742/ (Markdown: https://insights.sbomify.com/CVE-2018-20742/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-20742
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-20742
- OSV: https://osv.dev/vulnerability/CVE-2018-20742

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-20742/
Summaries are generated and may contain mistakes; the official description above is the record.