From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: libc-alpha@sourceware.org
Cc: adhemerval.zanella@linaro.org, fweimer@redhat.com
Subject: [PATCH 0/3] Fixes for CVE-2021-3998 and CVE-2021-3999
Date: Tue, 18 Jan 2022 14:37:25 +0530 [thread overview]
Message-ID: <20220118090728.1825487-1-siddhesh@sourceware.org> (raw)
Add functions to make directory trees with paths longer than PATH_MAX
and use them to test fixes for CVE-2021-3998 and CVE-2021-3999.
Tested on x86_64. Hurd build seems to already been broken, so I was
unable to test it.
Siddhesh Poyarekar (3):
support: Add helpers to create paths longer than PATH_MAX
realpath: Set errno to ENAMETOOLONG for result larger than PATH_MAX
[BZ #28770]
getcwd: Set errno to ERANGE for size == 1 (CVE-2021-3999)
NEWS | 10 +
stdlib/Makefile | 1 +
stdlib/canonicalize.c | 12 +-
stdlib/tst-realpath-toolong.c | 48 ++++
support/temp_file.c | 157 ++++++++++-
support/temp_file.h | 11 +
sysdeps/posix/getcwd.c | 7 +
sysdeps/unix/sysv/linux/Makefile | 7 +-
sysdeps/unix/sysv/linux/getcwd.c | 7 +
.../unix/sysv/linux/tst-getcwd-smallbuff.c | 245 ++++++++++++++++++
10 files changed, 494 insertions(+), 11 deletions(-)
create mode 100644 stdlib/tst-realpath-toolong.c
create mode 100644 sysdeps/unix/sysv/linux/tst-getcwd-smallbuff.c
--
2.34.1
next reply other threads:[~2022-01-18 9:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 9:07 Siddhesh Poyarekar [this message]
2022-01-18 9:07 ` [PATCH 1/3] support: Add helpers to create paths longer than PATH_MAX Siddhesh Poyarekar
2022-01-18 19:42 ` Adhemerval Zanella
2022-01-19 1:33 ` Siddhesh Poyarekar
2022-01-18 9:07 ` [PATCH 2/3] realpath: Set errno to ENAMETOOLONG for result larger than PATH_MAX [BZ #28770] Siddhesh Poyarekar
2022-01-18 19:43 ` Adhemerval Zanella
2022-01-18 9:07 ` [PATCH 3/3] getcwd: Set errno to ERANGE for size == 1 (CVE-2021-3999) Siddhesh Poyarekar
2022-01-18 11:52 ` Andreas Schwab
2022-01-18 13:10 ` Siddhesh Poyarekar
2022-01-18 13:13 ` Andreas Schwab
2022-01-18 13:16 ` Siddhesh Poyarekar
2022-01-18 13:30 ` Andreas Schwab
2022-01-18 13:33 ` Siddhesh Poyarekar
2022-01-18 13:41 ` Andreas Schwab
2022-01-18 13:45 ` Siddhesh Poyarekar
2022-01-18 13:56 ` Siddhesh Poyarekar
2022-01-18 13:57 ` Andreas Schwab
2022-01-18 14:40 ` Siddhesh Poyarekar
2022-01-18 13:59 ` Adhemerval Zanella
2022-01-18 14:44 ` Siddhesh Poyarekar
2022-01-18 16:30 ` Adhemerval Zanella
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=20220118090728.1825487-1-siddhesh@sourceware.org \
--to=siddhesh@sourceware.org \
--cc=adhemerval.zanella@linaro.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@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: 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).