2014-11-17 08:49:59 -0500, Greg Wooledge:
[...]
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6278 is the
> REAL bug. This is the root cause of all the remote exploitation
> badness. The patches which fix this problem fix remote exploitation
> of ALL the dumb parser bugs by closing of
On Mon, Nov 17, 2014 at 04:22:53PM +, Stephane Chazelas wrote:
> The real bug doesn't have a CVE attached to it because it's not
> a vulnerability or bug. It was "allowing the bash parser to be
> exposed to untrusted data", more a very unsafe design that was
> allowing any minor bug to turn int
On Mon, Nov 17, 2014 at 04:30:07PM +0800, Jack wrote:
> As title, what difference between CVE-2014-7187 and CVE-2014-6278 ?
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-7187 says
"Off-by-one error in the read_token_word function in parse.y"
So it's just another dumb parser bug, nothing
On 10/10/2014 08:00 AM, Nabiałek, Wojciech wrote:
>
> This code is not mine, refer to:
> http://stevejenkins.com/blog/2014/09/how-to-manually-update-bash-to-patch-shellshock-bug-on-older-fedora-based-systems/
> Exploit 5.
That blog is wrong. Here's how you test if your shell is vulnerable:
On 10/10/14, 10:00 AM, Nabiałek, Wojciech wrote:
> [root@e-mail wojtek]# (for x in {1..200} ; do echo "for x$x in ; do :"; done;
> for x in {1..200} ; do echo done ; done) | bash || echo "CVE-2014-7187
> vulnerable, word_lineno"
> bash: line 2: `x{1..200}': not a valid identifier
> CVE-2014-7187
On Fri, Oct 10, 2014 at 02:00:41PM +, Nabia??ek, Wojciech wrote:
> Difference is in version number, mine is 4.3.30(3), your 4.3.30(2)
The number in parentheses is simply how many times Bash has been compiled
in the current source tree. If you apply a new patch and run "make"
again, the number
PM
To: Nabiałek, Wojciech; bug-bash@gnu.org
Cc: chet.ra...@case.edu
Subject: Re: CVE-2014-7187
On 10/10/14, 4:03 AM, Nabiałek, Wojciech wrote:
> Hi,
>
> Bash 4.3 after patch 30 is still vulnerable for shellshock CVE-2014-7187.
No, it's not.
> (for x in {1..200} ; do echo &quo
On 10/10/14, 4:03 AM, Nabiałek, Wojciech wrote:
> Hi,
>
> Bash 4.3 after patch 30 is still vulnerable for shellshock CVE-2014-7187.
No, it's not.
> (for x in {1..200} ; do echo "for x$x in ; do :"; done; for x in {1..200} ;
> do echo done ; done) | bash || echo "CVE-2014-7187 vulnerable, word_l
