Bug 1535667 - glibc: Information leak via glibc finished thread cache
Summary: glibc: Information leak via glibc finished thread cache
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1535668 1535669 1546604 1546605
Blocks: 1535681
TreeView+ depends on / blocked
 
Reported: 2018-01-17 20:56 UTC by Pedro Sampaio
Modified: 2021-02-17 00:56 UTC (History)
15 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-20 07:45:17 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Sourceware 22852 0 P2 UNCONFIRMED Thread stack and heap caches 2019-12-12 19:27:09 UTC

Description Pedro Sampaio 2018-01-17 20:56:34 UTC 
A flaw was found in glibc. GNU Libc have special caches to keep stacks and heaps of finished threads. This behavior may break ASRL by leaking addresses of ended thread stack or heap.
Comment 5 Huzaifa S. Sidhpurwala 2018-01-30 07:00:42 UTC 
Statement:

This flaw can be used to leak addresses of data objects allocated on the stack or the heap. Since ASLR (Address Space Layout Randomization) is a post exploitation mitigation measure, Red Hat Product Security does not consider this as a security flaw, but rather a security hardening.
Comment 6 Doran Moppert 2018-02-19 01:47:49 UTC 
Upstream bug:

https://sourceware.org/bugzilla/show_bug.cgi?id=22852
Comment 7 Doran Moppert 2018-02-19 01:48:17 UTC 
Created glibc tracking bugs for this issue:

Affects: fedora-all [bug 1546605]


Created glibc-arm-linux-gnu tracking bugs for this issue:

Affects: fedora-all [bug 1546604]
Comment 8 Adam Mariš 2018-03-01 11:00:26 UTC 
Reference:

http://www.openwall.com/lists/oss-security/2018/02/27/5
Note You need to log in before you can comment on or make changes to this bug.