From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: libc-alpha@sourceware.org
Cc: Florian Weimer <fweimer@redhat.com>
Subject: Security implications of debugging features
Date: Mon, 12 Jul 2021 15:31:00 +0530 [thread overview]
Message-ID: <4d9d675f-cffa-4a5f-0af2-3be56532ce67@gotplt.org> (raw)
Hi,
It occurred to me that our security exceptions are silent on our policy
with debugging features. This was specifically in the context of mcheck
but I think it extends to other debugging features too. mcheck is
technically a supported glibc feature and may have been used in code
bases for a while. However given the lack of mcheck bugs (and boy is it
buggy!), the latter seems to be not as common.
Given that debugging features must not be enabled in production, should
we add the following exception for our security process? I've kept the
wording generic to cover any debugging features (source based or
otherwise) that I may have missed or we end up adding in future.
~~~~~~~~~~
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.
~~~~~~~~~~
Siddhesh
next reply other threads:[~2021-07-12 10:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-12 10:01 Siddhesh Poyarekar [this message]
2021-07-12 10:03 ` Security implications of debugging features Florian Weimer via Libc-alpha
2021-07-12 10:12 ` Siddhesh Poyarekar
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=4d9d675f-cffa-4a5f-0af2-3be56532ce67@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).