oss-security - RE: more bash parser bugs (CVE-2014-6277, CVE-2014-6278)

Follow @Openwall on Twitter for new release announcements and other news

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <3230301C09DEF9499B442BBE162C5E4825755BC7@SESTOEX04.enea.se>
Date: Thu, 2 Oct 2014 10:38:54 +0000
From: Sona Sarmadi <sona.sarmadi@...a.com>
To: "oss-security@...ts.openwall.com" <oss-security@...ts.openwall.com>
CC: Shawn <citypw@...il.com>
Subject: RE: more bash parser bugs (CVE-2014-6277,
 CVE-2014-6278)

Thanks Michal,

> * CVE-2014-6277 - uninitialized memory issue, almost certainly RCE found by
> me. No specific patch yet.

According to shellshock  test (https://shellshocker.net/shellshock_test.sh) 
Florian's patch (Gnu patch bash43-027)  and all other GNU patches (bash43-025 , 
bash43-026   & bash43-027 ) seems to have solved all so far known shellshock  
vulnerabilities.  

root@...uarm:~# ./shellshock_test.sh
CVE-2014-6271 (original shellshock): not vulnerable bash: shellshocker: command not found
CVE-2014-6278 (Florian's patch): not vulnerable
CVE-2014-7169 (taviso bug): not vulnerable
CVE-2014-//// (exploit 3 on http://shellshocker.net/): not vulnerable
CVE-2014-7186 (redir_stack bug): not vulnerable
CVE-2014-7187 (nested loops off by one): not vulnerable

I guess CVE-2014-//// in the "shellshock_test.sh" should be CVE-2014-6277, right?

Thanks
/Sona

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.