Vulnerability Details : CVE-2020-6838
Potential exploit
In mruby 2.1.0, there is a use-after-free in hash_values_at in mrbgems/mruby-hash-ext/src/hash-ext.c.
Vulnerability category: Memory Corruption
Products affected by CVE-2020-6838
- cpe:2.3:a:mruby:mruby:2.1.0:*:*:*:*:*:*:*
Exploit prediction scoring system (EPSS) score for CVE-2020-6838
0.42%
Probability of exploitation activity in the next 30 days
EPSS Score History
~ 61 %
Percentile, the proportion of vulnerabilities that are scored at or less
CVSS scores for CVE-2020-6838
| Base Score | Base Severity | CVSS Vector | Exploitability Score | Impact Score | Score Source | First Seen |
|---|---|---|---|---|---|---|
|
7.5
|
HIGH | AV:N/AC:L/Au:N/C:P/I:P/A:P |
10.0
|
6.4
|
NIST | |
|
9.8
|
CRITICAL | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
3.9
|
5.9
|
NIST |
CWE ids for CVE-2020-6838
-
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.Assigned by: nvd@nist.gov (Primary)
References for CVE-2020-6838
-
https://github.com/mruby/mruby/issues/4926
heap use after free in hash_values_at in mrbgems/mruby-hash-ext/src/hash-ext.c:33 · Issue #4926 · mruby/mruby · GitHubExploit;Third Party Advisory
Jump to