Bug 278161 - (CVE-2007-4660, CVE-2007-4661) CVE-2007-4661 php size calculation in chunk_split
CVE-2007-4661 php size calculation in chunk_split
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
: Reopened
Depends On: 297901
  Show dependency treegraph
Reported: 2007-09-05 06:32 EDT by Joe Orton
Modified: 2010-01-28 17:59 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-01-28 17:59:17 EST
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 Joe Orton 2007-09-05 06:32:07 EDT

# Fixed size calculation in chunk_split() (Reported by Gerhard Wagner)
Comment 2 Joe Orton 2007-09-05 08:58:47 EDT
This issue was due to an incomplete fix for CVE-2007-2872 (CVE-2007-2872), which
has not been applied in Red Hat Enterprise Linux v2-5, nor Red Hat Application
Stack v1.
Comment 5 Vincent Danen 2010-01-28 17:59:17 EST
I'm also adding CVE-2007-4660 to this issue as there is some confusion surrounding CVE-2007-4660 and how it pertains to CVE-2007-4661.

CVE-2007-2872 was partially fixed in upstream PHP 5.2.3, but the code remained vulnerable to attack.  This remaining vulnerability was named CVE-2007-4661.  While this was fixed upstream in PHP 5.2.4, it took two separate commits to fully fix it, resulting in (likely by mistake) two separate entries in the NEWS file, which resulted in CVE-2007-4660 being assigned to the second (arguably duplicate) CVE.

Because the incomplete fix for CVE-2007-2872 had not been applied to PHP packages in Red Hat Enterprise Linux 2 through 5, nor Red Hat Application Stack v1, neither CVE-2007-4660 or CVE-2007-4661 are applicable.  The fix provided for Red Hat Application Stack v2 corrected both CVEs, via RHSA-2007:0917:


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