public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/109446] Possible destination array overflow without diagnosis in memcpy Date: Wed, 12 Apr 2023 08:05:23 +0000 [thread overview] Message-ID: <bug-109446-4-DgVFmOgYTT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109446-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109446 --- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> --- The problem here is that we normally preserve memcpy calls and then __interceptor_memcpy is used from the run-time library. However, in this case the second argument of memcpy is a known constant and we convert it to: MEM <unsigned char[64]> [(char * {ref-all})_7] = MEM <unsigned char[64]> [(char * {ref-all})&txt]; for such an assignment we only check the beginning and the end of the chunk and we miss the overflow.
next prev parent reply other threads:[~2023-04-12 8:05 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-07 15:47 [Bug sanitizer/109446] New: " mohamed.selim at dxc dot com 2023-04-11 11:02 ` [Bug sanitizer/109446] " mohamed.selim at dxc dot com 2023-04-11 13:33 ` xry111 at gcc dot gnu.org 2023-04-12 8:05 ` marxin at gcc dot gnu.org [this message] 2023-04-12 8:08 ` xry111 at gcc dot gnu.org 2023-04-12 8:10 ` marxin at gcc dot gnu.org 2023-04-12 8:46 ` rguenth at gcc dot gnu.org 2023-04-12 8:52 ` jakub at gcc dot gnu.org 2023-04-12 8:59 ` rguenth at gcc dot gnu.org 2023-04-12 9:01 ` marxin at gcc dot gnu.org 2023-04-12 9:04 ` pinskia at gcc dot gnu.org 2023-04-12 9:07 ` marxin at gcc dot gnu.org 2023-04-12 9:18 ` rguenther at suse dot de 2023-04-12 11:16 ` xry111 at gcc dot gnu.org
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-109446-4-DgVFmOgYTT@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.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: linkBe 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).