Bug 152571 - CAN-2004-1772 buffer overflow with -o option
CAN-2004-1772 buffer overflow with -o option
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: sharutils (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Ngo Than
Jay Turner
: Security
Depends On:
  Show dependency treegraph
Reported: 2005-03-30 09:16 EST by Josh Bressers
Modified: 2015-01-07 19:09 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-04-26 12:31:28 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Josh Bressers 2005-03-30 09:16:09 EST
Stack-based buffer overflow in shar in GNU sharutils 4.2.1 allows local users to
execute arbitrary code via a long -o command line argument.

To test this:
shar -o `perl -e 'print "A"x2000'`

A patch is located here:
Comment 1 Josh Bressers 2005-03-30 09:16:55 EST
This issue also affects RHEL2.1
Comment 2 Ngo Than 2005-03-30 18:18:06 EST
it's fixed in sharutils-4.2.1-8.8.x (rhel-2) and sharutils-4.2.1-16.1 (rhel3)
Comment 3 Jay Turner 2005-03-31 01:21:55 EST
sharutils-4.2.1-16.1 is in 3.0E-errata-candidate
sharutils-4.2.1-8.8.x is in 2.1AS-errata-candidate

None of these have been released in errata, as the most recent errata was for
2.1 only and included sharutils-4.2.1-8.7.x.  Reopening this issue.
Comment 4 Ngo Than 2005-04-14 07:13:46 EDT
it's fixed in sharutils-4.2.1-8.9.x (rhel-2) and sharutils-4.2.1-16.2 (rhel3)
Comment 5 Josh Bressers 2005-04-26 12:31:28 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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