From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org
Subject: printf with %n directives
Date: Tue, 20 Feb 2024 16:46:22 +0100 [thread overview]
Message-ID: <5136090.7x91mkYCy2@nimes> (raw)
In <https://lists.gnu.org/archive/html/bug-gnulib/2023-08/msg00033.html> I wrote:
> I cannot guarantee that Gnulib will be able to support %n
> in the long run. The "security-aware community" are filing CVEs here and
> there; %n is among their targets (it has already been disabled from libc
> on Ubuntu, macOS, and MSVC); and I don't know when they will discover
> that Gnulib still enables it.
The way I propose to do it:
- Remove the support for the %n directives from all *printf* modules
by default.
- Add a new module 'printf-with-n-directive' that re-enables this support
in all these modules.
- Add a NEWS entry to notify the packages.
This way, most packages that use Gnulib *printf will be immune against
possible CVEs in this area.
I'm also considering making the same move in GNU libintl.
Bruno
next reply other threads:[~2024-02-20 15:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 15:46 Bruno Haible [this message]
2024-02-21 14:54 ` printf with %n directives Bruno Haible
2024-02-23 12:09 ` Bruno Haible
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://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5136090.7x91mkYCy2@nimes \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.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).