Bug 412221 (CVE-2007-6039)

Summary: CVE-2007-6039 PHP crash in various functions
Product: [Other] Security Response Reporter: Mark J. Cox <mjc>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED WONTFIX QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: unspecifiedCC: jorton
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
URL: http://nvd.nist.gov/nvd.cfm?cvename=CVE-2007-6039
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-12-05 19:05:51 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:

Description Mark J. Cox 2007-12-05 15:44:58 UTC
Common Vulnerabilities and Exposures assigned an identifier CVE-2007-6039 to the following vulnerability:

PHP 5.2.5 and earlier allows context-dependent attackers to cause a denial of service (application crash) via a long string in (1) the domain parameter to the dgettext function, the message parameter to the (2) dcgettext or (3) gettext function, the msgid1 parameter to the (4) dngettext or (5) ngettext function, or (6) the classname parameter to the stream_wrapper_register function.  NOTE: this might not be a vulnerability in most web server environments that support multiple threads, unless this issue can be demonstrated for code execution.

References:

http://www.securityfocus.com/archive/1/archive/1/483648/100/0/threaded
http://www.securityfocus.com/archive/1/archive/1/483644/100/0/threaded
http://www.securityfocus.com/bid/26426
http://www.securityfocus.com/bid/26428
http://securityreason.com/securityalert/3365
http://securityreason.com/securityalert/3366
http://xforce.iss.net/xforce/xfdb/38443
http://xforce.iss.net/xforce/xfdb/38442

Comment 1 Joe Orton 2007-12-05 16:32:40 UTC
The arguments to the functions in question should always be under the control of
the script author, rather than untrusted script input, so these issues would not
be treated as security-sensitive.

(See also bug 169857)