Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [day] [month] [year] [list]
Date: Fri, 26 Sep 2014 18:06:45 +0100
From: Gennady Kupava <>
Subject: Fwd: CVE-2014-6271: remote code execution through bash

The way how bash exports functions is really scary:

1. You can set both variable and export function with same name.
$ f () { a; }
$ export -f f
$ export f=3
$ echo $f
$ ksh
$ cat /proc/$$/environ|xargs -0 -n1|grep -w f
f=() {  a
$ echo $f

SUS says storing two environment varianles with same name is undefined

2. Bash partially hides environment variable holding function:
$ f () { a; }
$ export -f f
$ echo $f
[ nothing ]

Both things above look like good grounds for hackers.


Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.