From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 1198E397CF10; Fri,  8 May 2020 16:44:30 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1198E397CF10
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug malloc/25945] ASLR information leak via Safe-Linking and tcache
 or fastbin chunks.
Date: Fri, 08 May 2020 16:44:29 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: malloc
X-Bugzilla-Version: 2.26
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: carlos at redhat dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: security?
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-25945-131-pzxZCF1Z5k@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-25945-131@http.sourceware.org/bugzilla/>
References: <bug-25945-131@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: glibc-bugs@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Glibc-bugs mailing list <glibc-bugs.sourceware.org>
List-Unsubscribe: <http://sourceware.org/mailman/options/glibc-bugs>,
 <mailto:glibc-bugs-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/glibc-bugs/>
List-Help: <mailto:glibc-bugs-request@sourceware.org?subject=help>
List-Subscribe: <http://sourceware.org/mailman/listinfo/glibc-bugs>,
 <mailto:glibc-bugs-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Fri, 08 May 2020 16:44:30 -0000

https://sourceware.org/bugzilla/show_bug.cgi?id=3D25945

--- Comment #5 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Florian Weimer from comment #4)
> I'm not sure if this actually eligible for a CVE ID because it is an
> unreleased feature.  I've asked here:
>=20
> <https://www.openwall.com/lists/oss-security/2020/05/08/3>
>=20
> It's also a bug in a mitigation measure that requires another application
> bug in order to matter, and we usually do not treat those bugs as
> vulnerabilities in their own right.

I also appreciate that this is that it does not encourage prompt disclosure.

I will do my best to give positive incentive for prompt disclosure.

The things that are within my control are:

- Recognition with git authorship for patches you created.
  - See https://sourceware.org/glibc/wiki/Contribution%20checklist for how =
to
submit a patch and specifically the copyright requirements.

- Recognition with "Reported-by:" markup in git commit messages (if you are=
 not
the patch author).

- Recognition with your name in the project NEWS for the release as the
reporter.

Please feel free to suggest any other actions I can take to provide incenti=
ve.

Regarding the assignment of the CVE ID, like Florian says, we're gathering
consensus on this for unreleased products.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=