public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "siddhesh at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/27083] Unsafe unbounded alloca in addmntent Date: Tue, 22 Dec 2020 16:05:28 +0000 [thread overview] Message-ID: <bug-27083-131-SxYqNPYvHr@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27083-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27083 Siddhesh Poyarekar <siddhesh at sourceware dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |2.33 Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #3 from Siddhesh Poyarekar <siddhesh at sourceware dot org> --- Fixed in master: commit 9798906a426fc458b949271bcc9b8ad1608de867 (HEAD -> master) Author: Siddhesh Poyarekar <siddhesh@sourceware.org> Date: Tue Dec 22 17:18:12 2020 +0530 addmntent: Remove unbounded alloca usage from getmntent [BZ#27083] The addmntent function replicates elements of struct mnt on stack using alloca, which is unsafe. Put characters directly into the stream, escaping them as they're being written out. Also add a test to check all escaped characters with addmntent and getmntent. -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2020-12-22 16:05 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-16 14:12 [Bug libc/27083] New: " siddhesh at sourceware dot org 2020-12-16 14:18 ` [Bug libc/27083] " siddhesh at sourceware dot org 2020-12-16 16:32 ` siddhesh at sourceware dot org 2020-12-18 16:04 ` siddhesh at sourceware dot org 2020-12-22 16:05 ` siddhesh at sourceware dot org [this message]
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-27083-131-SxYqNPYvHr@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).