Vulnerability Details : CVE-2019-7309
In the GNU C Library (aka glibc or libc6) through 2.29, the memcmp function for the x32 architecture can incorrectly return zero (indicating that the inputs are equal) because the RDX most significant bit is mishandled.
Products affected by CVE-2019-7309
- cpe:2.3:a:gnu:glibc:*:*:*:*:*:*:x86:*
Exploit prediction scoring system (EPSS) score for CVE-2019-7309
0.09%
Probability of exploitation activity in the next 30 days
EPSS Score History
~ 35 %
Percentile, the proportion of vulnerabilities that are scored at or less
CVSS scores for CVE-2019-7309
| Base Score | Base Severity | CVSS Vector | Exploitability Score | Impact Score | Score Source | First Seen |
|---|---|---|---|---|---|---|
|
2.1
|
LOW | AV:L/AC:L/Au:N/C:N/I:N/A:P |
3.9
|
2.9
|
NIST | |
|
5.5
|
MEDIUM | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
1.8
|
3.6
|
NIST |
References for CVE-2019-7309
-
http://www.securityfocus.com/bid/106835
GNU glibc CVE-2019-7309 Local Denial of Service VulnerabilityThird Party Advisory;VDB Entry
-
https://security.gentoo.org/glsa/202006-04
glibc: Multiple vulnerabilities (GLSA 202006-04) — Gentoo security
-
https://sourceware.org/ml/libc-alpha/2019-02/msg00041.html
H.J. Lu - Re: [PATCH] x86-64 memcmp: Use unsigned Jcc instructions on sizeMailing List;Third Party Advisory
-
https://sourceware.org/bugzilla/show_bug.cgi?id=24155
24155 – (CVE-2019-7309) x32 memcmp can treat positive length as 0 (if sign bit in RDX is set) (CVE-2019-7309)Issue Tracking;Exploit;Third Party Advisory
Jump to