Bug 40400 - man 1.5h1-10 has an exploitable overflow
Summary: man 1.5h1-10 has an exploitable overflow
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: man   
(Show other bugs)
Version: 7.0
Hardware: i386 Linux
Target Milestone: ---
Assignee: Bernhard Rosenkraenzer
QA Contact: Aaron Brown
Depends On:
TreeView+ depends on / blocked
Reported: 2001-05-13 17:35 UTC by Need Real Name
Modified: 2007-04-18 16:33 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-05-13 18:22:43 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2001:069 normal SHIPPED_LIVE : Updated man package fixing security problems available 2001-05-13 04:00:00 UTC

Description Need Real Name 2001-05-13 17:35:11 UTC
Description of Problem:

man 1.5h1-10 (version released with rh7.0) has a heap based overflow
in man.c, get_section_list() function. The check 

      if (end == NULL || i + 1 == sizeof (tmp_section_list))
should be
      if (end == NULL || i + 1 == (sizeof (tmp_section_list) /

There exists an exploit for gid man.

How Reproducible:

Make a section list with over 100 elements in it.

Steps to Reproduce:
1. man -S `perl -e 'print ":" x 101'` ls

Actual Results:

Segmentation fault

Expected Results:

No manual entry for ls

Additional Information:
A root exploit from gid man also exists.

Comment 1 Bernhard Rosenkraenzer 2001-05-13 18:22:38 UTC
Quick fix: Update to the versions from 7.1 or rawhide (preferred).
I'll take care of errataing this now.

Comment 2 Bernhard Rosenkraenzer 2001-05-21 18:38:10 UTC
The errata package just passed QA - closing this bug.

Comment 3 Bernhard Rosenkraenzer 2001-05-21 18:39:50 UTC
By the way, I could not find any information about a root exploit from gid man 
anywhere on the net.
If this is indeed true, please open a new bug report with information on this.

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