public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "corbellini.andrea at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/15763] New: shm_open/unlink let you write outside SHMDIR Date: Sat, 20 Jul 2013 10:55:00 -0000 [thread overview] Message-ID: <bug-15763-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=15763 Bug ID: 15763 Summary: shm_open/unlink let you write outside SHMDIR Product: glibc Version: 2.18 Status: NEW Severity: normal Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: corbellini.andrea at gmail dot com CC: drepper.fsp at gmail dot com shm_open() and shm_unlink() accept relative paths. As the test case below demonstrates, if you give a relative path to shm_open, you will be able to open files anywhere in the system (assuming that you have the right permissions). Test case: #include <fcntl.h> int main (void) { shm_open ("../../tmp/abc", O_CREAT | O_RDWR, 0666); perror ("shm_open"); } Expected output: shm_open: Invalid argument Actual output: shm_open: Success -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2013-07-20 10:55 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-07-20 10:55 corbellini.andrea at gmail dot com [this message] 2013-07-20 17:04 ` [Bug libc/15763] " bugdal at aerifal dot cx 2013-07-20 18:45 ` corbellini.andrea at gmail dot com 2013-07-20 19:09 ` bugdal at aerifal dot cx 2013-07-20 20:40 ` corbellini.andrea at gmail dot com 2013-10-31 13:03 ` neleai at seznam dot cz 2014-06-13 13:21 ` fweimer at redhat dot 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-15763-131@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).