public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug localedata/17137] New: Directory traversal in locale environment handling (CVE-2014-0475)
Date: Wed, 09 Jul 2014 16:09:00 -0000 [thread overview]
Message-ID: <bug-17137-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=17137
Bug ID: 17137
Summary: Directory traversal in locale environment handling
(CVE-2014-0475)
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: localedata
Assignee: fweimer at redhat dot com
Reporter: fweimer at redhat dot com
CC: libc-locales at sourceware dot org
Flags: security+
Stephane Chazelas reported (via Debian) a directory traversal issue in locale
handling in glibc. glibc accepts relative paths with ".." components in the
LC_* and LANG variables. Together with typical OpenSSH configurations (with
suitable AcceptEnv settings in sshd_config), this could conceivably be used to
bypass ForceCommand restrictions, assuming the attacker has sufficient level of
access to a file system location on the host to create crafted locale
definitions there.
Due to an existing AT_SECURE check, SUID/SGID binaries are not directly
vulnerable, but this protection will not necessarily extend to child processes.
For sudo, this is mitigated by the env_check defaults, so even configurations
which list LC_* variables among env_keep should be safe.
I will post patches to libc-alpha for review shortly.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2014-07-09 16:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 16:09 fweimer at redhat dot com [this message]
2014-07-10 15:21 ` [Bug localedata/17137] " cvs-commit at gcc dot gnu.org
2014-07-10 16:02 ` fweimer at redhat dot com
2014-07-10 23:20 ` cvs-commit at gcc dot gnu.org
2014-08-28 12:02 ` cvs-commit at gcc dot gnu.org
2014-09-05 13:16 ` cvs-commit at gcc dot gnu.org
2015-01-16 16:59 ` cvs-commit at gcc dot gnu.org
2015-01-16 17:02 ` cvs-commit at gcc dot gnu.org
2015-01-29 18:50 ` cvs-commit at gcc dot gnu.org
2015-02-23 14:23 ` cvs-commit at gcc dot gnu.org
2015-02-23 15:02 ` 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-17137-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: 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).