Bug 1737445 (CVE-2019-1010025) - CVE-2019-1010025 glibc: information disclosure of heap addresses of pthread_created thread
Summary: CVE-2019-1010025 glibc: information disclosure of heap addresses of pthread_c...
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2019-1010025
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1737446
Blocks: 1737447
TreeView+ depends on / blocked
 
Reported: 2019-08-05 11:30 UTC by Dhananjay Arunesh
Modified: 2021-02-16 21:33 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-07 01:18:18 UTC
Embargoed:


Attachments (Terms of Use)

Description Dhananjay Arunesh 2019-08-05 11:30:46 UTC
GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may
guess the heap addresses of pthread_created thread. The component is: glibc.

Reference:
https://sourceware.org/bugzilla/show_bug.cgi?id=22853

Comment 1 Dhananjay Arunesh 2019-08-05 11:31:11 UTC
Created glibc tracking bugs for this issue:

Affects: fedora-all [bug 1737446]

Comment 3 Marco Benatto 2019-08-06 21:43:15 UTC
The information disclosure mentioned by CVE-2019-1010025 is not considered a vulnerability and its fix should be considered a hardening instead.
Although it's possible to eventually leak the thread heap's address by passing the ASLR mechanism, this bug is not exploitable by itself. An attack can not use this directly to perform any unexpected action, although this can be used to exploit any other unrelated software which consumes glibc's pthread API.

Comment 4 Marco Benatto 2019-08-06 21:49:21 UTC
Statement:

This is does not affect the package glibc as shipped with Red Hat Enterprise Linux 5, 6,7 and 8. The bug related to this CVE is not exploitable.

Comment 5 Product Security DevOps Team 2019-08-07 01:18:18 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2019-1010025


Note You need to log in before you can comment on or make changes to this bug.