CVE-2019-1010025: Medium severity GNU glibc vulnerability
Published Jul 15, 2019
·Updated
DISPUTED GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may guess the heap addresses of pthreadcreated thread. The component is: glibc. NOTE: the vendor's position is "ASLR bypass itself is not a vulnerability."
Affected Software
2 affected components
GNU glibc
debian/glibc<=2.31-13+deb11u11, <=2.31-13+deb11u13, <=2.36-9+deb12u13, <=2.36-9+deb12u7, <=2.41-12+deb13u2, <=2.42-13
Event History
Jul 15, 2019
CVE Published
via MITRE·03:11 AM
Data Sourced
via MITRE·03:11 AM
DescriptionWeakness
Disputed
04:15 AM
Data Sourced
via NVD·04:15 AM
DescriptionSeverityWeaknessAffected Software
Feb 20, 2026
Data Sourced
via Ubuntu·09:51 PM
RemedyDescriptionSeverityAffected Software
Data Sourced
via Launchpad·09:51 PM
Description
Mar 14, 2026
Data Sourced
via Debian·10:05 PM
DescriptionAffected Software
Frequently Asked Questions
1
What is CVE-2019-1010025?
CVE-2019-1010025 is a vulnerability in GNU Libc that allows an attacker to guess the heap addresses of pthread_created thread.
2
What is the impact of CVE-2019-1010025?
The impact of CVE-2019-1010025 is that an attacker may guess the heap addresses of pthread_created thread.
3
What is the component affected by CVE-2019-1010025?
The component affected by CVE-2019-1010025 is glibc.
4
What is the severity of CVE-2019-1010025?
The severity of CVE-2019-1010025 is medium.
5
How do I mitigate CVE-2019-1010025?
There is no known remedy to mitigate CVE-2019-1010025 at this time.