Skip to content
Fencer Intel
medium 4.3

CVE-2011-1398 json

The sapi_header_op function in main/SAPI.c in PHP before 5.3.11 and 5.4.x before 5.4.0RC2 does not check for %0D sequences (aka carriage re…

published 2012-08-30 14 y ago modified 2026-06-16 4 mo ago also EUVD-2011-1405

cvss
4.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
10.2%
EPSS 10.2% chance of exploitation in 30 days, percentile 95%
public exploits
1
Exploit-DB

Summary

The sapi_header_op function in main/SAPI.c in PHP before 5.3.11 and 5.4.x before 5.4.0RC2 does not check for %0D sequences (aka carriage return characters), which allows remote attackers to bypass an HTTP response-splitting protection mechanism via a crafted URL, related to improper interaction between the PHP header function and certain browsers, as demonstrated by Internet Explorer and Google Chrome.

Patch / fix

  • php RHEL 5 5.1.6-43.el5_10
  • php-gd RHEL 5 5.1.6-43.el5_10
  • php-cli RHEL 5 5.1.6-43.el5_10
  • php-dba RHEL 5 5.1.6-43.el5_10
  • php-pdo RHEL 5 5.1.6-43.el5_10
  • php-xml RHEL 5 5.1.6-43.el5_10
  • php-imap RHEL 5 5.1.6-43.el5_10
  • php-ldap RHEL 5 5.1.6-43.el5_10

red hat advisories RHSA-2013:1814RHSA-2013:1307RHSA-2013:0514

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2011-1398 updated cvss 4.3

PHP: sapi_header_op() %0D sequence handling security bypass

  • Red Hat Enterprise Linux (v. 5 server) php53 5.3.3-21.el5, php 5.1.6-43.el5_10, php53-gd 5.3.3-21.el5, php-gd 5.1.6-43.el5_10, php53-cli 5.3.3-21.el5, php53-dba 5.3.3-21.el5, +32 more
    fixed: vendor fix RHSA-2013:1814
  • Red Hat Enterprise Linux Desktop Optional (v. 6) php 5.3.3-22.el6, php-gd 5.3.3-22.el6, php-cli 5.3.3-22.el6, php-dba 5.3.3-22.el6, php-fpm 5.3.3-22.el6, php-pdo 5.3.3-22.el6, +20 more
    fixed: vendor fix RHSA-2013:0514
  • Red Hat Enterprise Linux Desktop Workstation (v. 5 client) php53 5.3.3-21.el5, php 5.1.6-43.el5_10, php53-gd 5.3.3-21.el5, php-gd 5.1.6-43.el5_10, php53-cli 5.3.3-21.el5, php53-dba 5.3.3-21.el5, +32 more
    fixed: vendor fix RHSA-2013:1814
  • Red Hat Enterprise Linux HPC Node (v. 6) php 5.3.3-22.el6, php-gd 5.3.3-22.el6, php-cli 5.3.3-22.el6, php-dba 5.3.3-22.el6, php-fpm 5.3.3-22.el6, php-pdo 5.3.3-22.el6, +20 more Red Hat Enterprise Linux HPC Node Optional (v. 6) php 5.3.3-22.el6, php-gd 5.3.3-22.el6, php-cli 5.3.3-22.el6, php-dba 5.3.3-22.el6, php-fpm 5.3.3-22.el6, php-pdo 5.3.3-22.el6, +20 more Red Hat Enterprise Linux Server (v. 6) php 5.3.3-22.el6, php-gd 5.3.3-22.el6, php-cli 5.3.3-22.el6, php-dba 5.3.3-22.el6, php-fpm 5.3.3-22.el6, php-pdo 5.3.3-22.el6, +20 more Red Hat Enterprise Linux Server Optional (v. 6) php 5.3.3-22.el6, php-gd 5.3.3-22.el6, php-cli 5.3.3-22.el6, php-dba 5.3.3-22.el6, php-fpm 5.3.3-22.el6, php-pdo 5.3.3-22.el6, +20 more Red Hat Enterprise Linux Workstation (v. 6) php 5.3.3-22.el6, php-gd 5.3.3-22.el6, php-cli 5.3.3-22.el6, php-dba 5.3.3-22.el6, php-fpm 5.3.3-22.el6, php-pdo 5.3.3-22.el6, +20 more Red Hat Enterprise Linux Workstation Optional (v. 6) php 5.3.3-22.el6, php-gd 5.3.3-22.el6, php-cli 5.3.3-22.el6, php-dba 5.3.3-22.el6, php-fpm 5.3.3-22.el6, php-pdo 5.3.3-22.el6, +20 more
    fixed: vendor fix RHSA-2013:0514

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. First public exploit (EDB-37688)
  2. Published

Exploit prediction

10.17% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-37688 PHP 5.3.11/5.4.0RC2 - 'header()' HTTP Header Injection remote, 2011-10-06

CVSS scores

assigned by version score vector
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N

Classification

Weakness
  • CWE-20 Improper Input Validation
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.