From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: Security implications of debugging features
Date: Mon, 12 Jul 2021 15:42:41 +0530 [thread overview]
Message-ID: <746d3148-7ea3-d204-6e76-6f1c2092643a@gotplt.org> (raw)
In-Reply-To: <87lf6bdf33.fsf@oldenburg.str.redhat.com>
On 7/12/21 3:33 PM, Florian Weimer wrote:
>> ~~~~~~~~~~
>> Debugging features
>>
>> glibc comes with a number of debugging features that allow developers
>> to isolate root causes of problems. Bugs in debugging features that
>> are enabled by explicitly compiling applications or glibc to use them
>> are not considered security vulnerabilities and will be treated as
>> regular bugs. Examples of such features are mcheck and mtrace, which
>> allow debugging and tracing of glibc malloc functions.
>>
>> Bugs in debugging features that are enabled by exporting an
>> environment variable in the environment of a program may for now be
>> considered security issues in a local context.
>> ~~~~~~~~~~
>
> I don't understand the second paragraph.
What I intend to convey is that bugs in debugging features won't be
considered remotely exploitable.
> I think we need to talk about AT_SECURE (SUID) mode in this context.
Could you elaborate on what you'd like mentioned? Would you like a note
that the dynamic linker wipes out debugging options when running setuid
binaries? It seems like a security claim (there could well be a bug in
there that negates it) and hence not suitable for this text.
Siddhesh
next prev parent reply other threads:[~2021-07-12 10:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-12 10:01 Security implications of debugging features Siddhesh Poyarekar
2021-07-12 10:03 ` Florian Weimer via Libc-alpha
2021-07-12 10:12 ` Siddhesh Poyarekar [this message]
2021-07-12 10:16 ` Florian Weimer via Libc-alpha
2021-07-12 10:28 ` Siddhesh Poyarekar
2021-07-12 10:41 ` Florian Weimer via Libc-alpha
2021-07-12 10:45 ` Siddhesh Poyarekar
2021-07-12 10:03 ` Siddhesh Poyarekar
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=746d3148-7ea3-d204-6e76-6f1c2092643a@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@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).