From: Frank Busse <f.busse@imperial.ac.uk>
To: 64229@debbugs.gnu.org
Subject: bug#64229: b2sum: heap-overflow in digest_check
Date: Thu, 22 Jun 2023 17:33:40 +0100 [thread overview]
Message-ID: <20230622173340.0906eb6c@gyali> (raw)
Hi,
KLEE reported a heap-overflow in b2sum (Coreutils 9.3). When running it
with:
$ printf '\n\n0A0BA0' | coreutils-9.3/bin/b2sum -c
(even '0BA0' seems to work on my machine) ASAN confirms the issue:
> #1 0x0000000000473de0 in __interceptor_strchr (s=<optimized out>, c=<optimized out>)
> #2 0x0000000000500a81 in digest_check (checkfile_name=0x7fffffffe69e "stdin") at /tmp/src/coreutils-9.3/src/digest.c:1216
> #3 0x00000000005005e9 in main (argc=3, argv=0x7fffffffe3a8) at /tmp/src/coreutils-9.3/src/digest.c:1607
Best,
Frank
next reply other threads:[~2023-06-22 16:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 16:33 Frank Busse [this message]
2023-06-22 20:48 ` bug#64229: b2sum: heap-overflow in digest_check Pádraig Brady
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-coreutils
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230622173340.0906eb6c@gyali \
--to=f.busse@imperial.ac.uk \
--cc=64229@debbugs.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).