bash crashed with SIGSEGV in strlen()

Bug #1378071 reported by David Gregory
258
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bash (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Tried to run vulnerability tester for ShellShock:

    curl https://shellshocker.net/shellshock_test.sh | bash

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: bash 4.3-10ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
Uname: Linux 3.16.0-20-generic x86_64
ApportVersion: 2.14.7-0ubuntu3
Architecture: amd64
Date: Mon Oct 6 15:20:52 2014
ExecutablePath: /bin/bash
InstallationDate: Installed on 2014-10-03 (3 days ago)
InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
ProcCmdline: bash -c f()\ {\ x()\ {\ _;};\ x()\ {\ _;}\ <<a;\ }
ProcEnviron:
 TERM=xterm
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fa67ca5c564 <strlen+148>: pcmpeqb (%rax),%xmm8
 PC (0x7fa67ca5c564) ok
 source "(%rax)" (0xdfdfdfdfdfdfdfc0) not located in a known VMA region (needed readable region)!
 destination "%xmm8" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: bash
StacktraceTop:
 strlen () at ../sysdeps/x86_64/strlen.S:137
 copy_redirect ()
 copy_redirects ()
 copy_command ()
 copy_function_def_contents ()
Title: bash crashed with SIGSEGV in strlen()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

CVE References

Revision history for this message
David Gregory (homeyd5) wrote :
tags: removed: need-amd64-retrace
Revision history for this message
Seth Arnold (seth-arnold) wrote :

With the prefix+suffix patches, this can no longer be exploited across privilege boundaries; we'll likely include these fixes at some point in the future but don't consider them a pressing issue any longer. For more details please see our CVE tracker: http://people.canonical.com/~ubuntu-security/cve/2014/CVE-2014-6277.html

Thanks

information type: Private Security → Public Security
Revision history for this message
Seth Arnold (seth-arnold) wrote :

Also, please, no one ever run any command along the line of "curl foo | bash" -- a malicious web server could easily give some friendly-looking content to a web browser but malware payload to curl.

Download the script, read the script, validate published signatures, and only then execute the script directly if you still trust it.

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

This should be fixed now by:
http://www.ubuntu.com/usn/usn-2380-1/

Changed in bash (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public Security information  
Everyone can see this security related information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.