CVE-2018-20742

Public Exploit

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.

Category

7.5
CVSS
Severity: High
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.24%
Third-Party Advisory github.com Third-Party Advisory github.com
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://github.com/ucbrise/opaque/issues/66 exploit third party advisory patch
https://github.com/ucbrise/opaque/commit/5ddda15d89f5ac82f4416208c5319ace4aecdc36 third party advisory patch

Frequently Asked Questions

What is the severity of CVE-2018-20742?
CVE-2018-20742 has been scored as a high severity vulnerability.
How to fix CVE-2018-20742?
To fix CVE-2018-20742, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2018-20742 being actively exploited in the wild?
It is possible that CVE-2018-20742 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.