Vulnerability Details : CVE-2018-20742
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.
Vulnerability category: Memory Corruption
Products affected by CVE-2018-20742
- cpe:2.3:a:ucbrise:opaque:*:*:*:*:*:*:*:*
Exploit prediction scoring system (EPSS) score for CVE-2018-20742
0.20%
Probability of exploitation activity in the next 30 days
EPSS Score History
~ 58 %
Percentile, the proportion of vulnerabilities that are scored at or less
CVSS scores for CVE-2018-20742
| Base Score | Base Severity | CVSS Vector | Exploitability Score | Impact Score | Score Source | First Seen |
|---|---|---|---|---|---|---|
|
5.0
|
MEDIUM | AV:N/AC:L/Au:N/C:N/I:P/A:N |
10.0
|
2.9
|
NIST | |
|
7.5
|
HIGH | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
3.9
|
3.6
|
NIST |
CWE ids for CVE-2018-20742
-
The product writes data past the end, or before the beginning, of the intended buffer.Assigned by: nvd@nist.gov (Primary)
References for CVE-2018-20742
-
https://github.com/ucbrise/opaque/issues/66
Security: No boundary check on `ocall_malloc` · Issue #66 · ucbrise/opaque · GitHubExploit;Patch;Third Party Advisory
-
https://github.com/ucbrise/opaque/commit/5ddda15d89f5ac82f4416208c5319ace4aecdc36
Check that ecall [user_check] pointers and ocall_malloc result pointe… · ucbrise/opaque@5ddda15 · GitHubPatch;Third Party Advisory
Jump to