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 libc/32094] _nl_find_msg bug in glibc
Date: Mon, 19 Aug 2024 15:44:03 +0000 [thread overview]
Message-ID: <bug-32094-131-QkA5gv6U0H@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-32094-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=32094
Carlos O'Donell <carlos at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags| |security-
Resolution|--- |INVALID
Status|UNCONFIRMED |RESOLVED
CC| |carlos at redhat dot com
--- Comment #1 from Carlos O'Donell <carlos at redhat dot com> ---
We don't consider this a security bug. Application data files, like ELF files,
localization files, and translation; are assumed trusted, meaning that while we
should not crash on invalid input, this does not cross a trust boundary.
Marking this security-
We also don't consider it a bug that invalid files cause a crash. There might
be an opportunity to harden the code, but not at the expense of valid correctly
formed installations and programs.
If you want to improve the hardening of this code please file a new bug and we
can discuss the improvements.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2024-08-19 15:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-18 4:33 [Bug libc/32094] New: " bsdhenrymartin at gmail dot com
2024-08-19 15:44 ` carlos at redhat dot com [this message]
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-32094-131-QkA5gv6U0H@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).