From: "sean@rogue-research.com" <sourceware-bugzilla@sourceware.org>
To: bzip2-devel@sourceware.org
Subject: [Bug bzip2/29280] New: Replace sprintf with safer snprintf
Date: Thu, 23 Jun 2022 15:42:44 +0000 [thread overview]
Message-ID: <bug-29280-11876@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29280
Bug ID: 29280
Summary: Replace sprintf with safer snprintf
Product: bzip2
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: bzip2
Assignee: nobody at sourceware dot org
Reporter: sean@rogue-research.com
CC: bzip2-devel at sourceware dot org
Target Milestone: ---
bzip2 has one call to sprintf in git master.
sprintf is dangerous because it's easy to overrun the buffer. Building on
OpenBSD and macOS produce compiler warnings upon any use of the function.
Would be nice to change this one use to snprintf, which takes the buffer size.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-06-23 15:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 15:42 sean@rogue-research.com [this message]
2022-10-25 22:59 ` [Bug bzip2/29280] " sean@rogue-research.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-29280-11876@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=bzip2-devel@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).