What is the severity of CVE-2011-1398?

CVE-2011-1398 has a medium severity level due to its potential to enable HTTP response-splitting attacks.

How do I fix CVE-2011-1398?

To fix CVE-2011-1398, upgrade PHP to version 5.3.11 or higher, or 5.4.0RC2 or higher.

Which versions of PHP are affected by CVE-2011-1398?

CVE-2011-1398 affects PHP versions prior to 5.3.11 and all versions of the 5.4.x branch before 5.4.0RC2.

What are the implications of CVE-2011-1398?

The implications of CVE-2011-1398 include the risk of remote attackers exploiting the vulnerability to manipulate HTTP headers.

Is there a workaround for CVE-2011-1398 if I cannot upgrade PHP?

There are no effective workarounds for CVE-2011-1398; upgrading PHP is the recommended solution.

Vulnerability/
CVE-2011-1398

medium

4.3

CWE

30/8/2012

6/8/2024

CVE-2011-1398: Input Validation

First published: Thu Aug 30 2012(Updated: )

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.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
PHP	<=5.3.10
PHP	=5.3.0
PHP	=5.3.1
PHP	=5.3.2
PHP	=5.3.3
PHP	=5.3.4
PHP	=5.3.5
PHP	=5.3.6
PHP	=5.3.7
PHP	=5.3.8
PHP	=5.3.9

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2011-1398?
CVE-2011-1398 has a medium severity level due to its potential to enable HTTP response-splitting attacks.
How do I fix CVE-2011-1398?
To fix CVE-2011-1398, upgrade PHP to version 5.3.11 or higher, or 5.4.0RC2 or higher.
Which versions of PHP are affected by CVE-2011-1398?
CVE-2011-1398 affects PHP versions prior to 5.3.11 and all versions of the 5.4.x branch before 5.4.0RC2.
What are the implications of CVE-2011-1398?
The implications of CVE-2011-1398 include the risk of remote attackers exploiting the vulnerability to manipulate HTTP headers.
Is there a workaround for CVE-2011-1398 if I cannot upgrade PHP?
There are no effective workarounds for CVE-2011-1398; upgrading PHP is the recommended solution.

agent/references
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/severity
agent/weakness
agent/author
agent/description
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
collector/nvd-historical
vendor/php
canonical/php
version/php/5.3.10
version/php/5.3.0
version/php/5.3.1
version/php/5.3.2
version/php/5.3.3
version/php/5.3.4
version/php/5.3.5
version/php/5.3.6
version/php/5.3.7
version/php/5.3.8
version/php/5.3.9

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2011-1398?
CVE-2011-1398 has a medium severity level due to its potential to enable HTTP response-splitting attacks.
How do I fix CVE-2011-1398?
To fix CVE-2011-1398, upgrade PHP to version 5.3.11 or higher, or 5.4.0RC2 or higher.
Which versions of PHP are affected by CVE-2011-1398?
CVE-2011-1398 affects PHP versions prior to 5.3.11 and all versions of the 5.4.x branch before 5.4.0RC2.
What are the implications of CVE-2011-1398?
The implications of CVE-2011-1398 include the risk of remote attackers exploiting the vulnerability to manipulate HTTP headers.
Is there a workaround for CVE-2011-1398 if I cannot upgrade PHP?
There are no effective workarounds for CVE-2011-1398; upgrading PHP is the recommended solution.