Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 3 product line. The current stable release is 3.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 140227

Summary: Potential insecurity in CGI.pm
Product: Red Hat Enterprise Linux 3 Reporter: Andreas Thienemann <andreas>
Component: perlAssignee: Chip Turner <cturner>
Status: CLOSED ERRATA QA Contact: David Lawrence <dkl>
Severity: low Docs Contact:
Priority: medium    
Version: 3.0CC: bressers, mjc
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: impact=low,public=20040127
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-02-07 16:42:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
better way of obtaining $script_name none

Description Andreas Thienemann 2004-11-21 12:42:28 UTC 
During a security audit of one of our perl-based webapplications we
noticed that there is a potential security problem in the CGI.pm
version included in RHEL3. Later issues of perl seems to have this fixed.

The problem lies in the way $script_name is obtained:
The s/some_client_provided_data/some_other_client_provided_data/ call
is a potential issue as the client can provide complicated regular
expressions which eat lots-o-ram [tm].
This could lead to a denial-of-service issue.

A patch for the RPM is attached.

Version-Release number of selected component (if applicable):
5.8.0-88.7
Comment 1 Andreas Thienemann 2004-11-21 12:44:07 UTC 
Created attachment 107134 [details]
better way of obtaining $script_name

This is the silent fix which seems to have been incorporated into recent perl
releases.
Comment 2 Mark J. Cox 2005-02-07 15:55:44 UTC 
This requires a valid regexp that will (to some extent) self match
after decoding, therefore this isn't going to be a siginificant DoS on
any reasonable system (there would be many better ways of doing a
DoS).  We're fixing it in an update due shortly however.
Comment 3 Josh Bressers 2005-02-07 16:42:40 UTC 
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.

http://rhn.redhat.com/errata/RHSA-2005-105.html