public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "huzaifas at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug math/25487] sinl() stack corruption from crafted input (CVE-2020-10029) Date: Wed, 12 Aug 2020 04:51:09 +0000 [thread overview] Message-ID: <bug-25487-131-YZxWj6Wsj4@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-25487-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=25487 Huzaifa Sidhpurwala <huzaifas at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |huzaifas at redhat dot com --- Comment #8 from Huzaifa Sidhpurwala <huzaifas at redhat dot com> --- Looking at the way crash is caused via pseudo-zero numbers and after running the poc through gdb, it seems like on systems in which glibc is not compiled with -fstack-protector-all, (which means the vuln function is not protected by stack-canaries), all that can be achieved is overwrite the stack and the return address with 0's. This can only cause a crash and jumping any other location seems very difficult to achieve if not impossible. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-08-12 4:51 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-25487-131@http.sourceware.org/bugzilla/> 2020-03-16 16:54 ` cvs-commit at gcc dot gnu.org 2020-03-16 16:54 ` cvs-commit at gcc dot gnu.org 2020-08-12 4:51 ` huzaifas at redhat dot com [this message] 2020-08-19 1:38 ` dominik.b.czarnota+bugzilla at gmail dot com 2021-09-21 0:53 ` cvs-commit 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-25487-131-YZxWj6Wsj4@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: 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).