Bug 492089 - zsh: Stack-based buffer overflow due improper escaping of the '!' character
Summary: zsh: Stack-based buffer overflow due improper escaping of the '!' character
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL: https://bugs.launchpad.net/ubuntu/+so...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-25 11:26 UTC by Jan Lieskovsky
Modified: 2019-09-29 12:29 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-04-01 12:19:44 UTC
Embargoed:


Attachments (Terms of Use)

Description Jan Lieskovsky 2009-03-25 11:26:17 UTC
A stack-based buffer overflow was found in the zsh command interpreter.
An attacker could use this flaw to cause a denial of service (zsh crash),
when providing a specially-crafted string as input to the zsh shell.

References:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=521108
https://bugs.launchpad.net/ubuntu/+source/zsh/+bug/333722

PoC:
Provide following string to zsh in interactive mode:

% AAAAAAAAAAAAAAAAAAAAAAAA!AAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

Please note the '!' character in the above string.
Also provide the above string to /bin/zsh without
newlines (they have been added only for better readability).

Comment 1 Jan Lieskovsky 2009-03-25 11:27:31 UTC
This issue affects all versions of the zsh package, as shipped
with Red Hat Enteprise Linux 2.1, 3, 4, and 5.

This issue affects all versions of the zsh package, as shipped
with Fedora releases of 9, 10, and devel.

Comment 2 Jan Lieskovsky 2009-03-25 12:35:07 UTC
The Red Hat Security Response Team has rated this issue as having
low security impact, a future update may address this flaw.
More information regarding issue severity can be found here:
http://www.redhat.com/security/updates/classification/


Note You need to log in before you can comment on or make changes to this bug.