public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
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 [thread overview]
Message-ID: <bug-25945-131-pzxZCF1Z5k@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25945-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25945
--- 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:
>
> <https://www.openwall.com/lists/oss-security/2020/05/08/3>
>
> 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 incentive.
Regarding the assignment of the CVE ID, like Florian says, we're gathering
consensus on this for unreleased products.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-05-08 16:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 3:35 [Bug malloc/25945] New: memory block return by tcache_get() may contain anather valid memory block pointer, leading to memory leak wangxuszcn at foxmail dot com
2020-05-08 9:51 ` [Bug malloc/25945] " wangxuszcn at foxmail dot com
2020-05-08 12:48 ` [Bug malloc/25945] memory block return by tcache_get() may contain anather valid memory block pointer, leading to information disclosure wangxuszcn at foxmail dot com
2020-05-08 13:03 ` wangxuszcn at foxmail dot com
2020-05-08 16:19 ` carlos at redhat dot com
2020-05-08 16:20 ` [Bug malloc/25945] ASLR information leak via Safe-Linking and tcache or fastbin chunks carlos at redhat dot com
2020-05-08 16:20 ` fweimer at redhat dot com
2020-05-08 16:23 ` fweimer at redhat dot com
2020-05-08 16:44 ` carlos at redhat dot com [this message]
2020-05-08 19:18 ` dj at redhat dot com
2020-05-09 3:40 ` wangxuszcn at foxmail dot com
2020-05-09 3:45 ` wangxuszcn at foxmail dot com
2020-05-13 15:22 ` carlos at redhat dot com
2020-05-15 2:04 ` wangxuszcn at foxmail dot com
2020-05-15 6:44 ` wangxuszcn at foxmail dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-25945-131-pzxZCF1Z5k@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).