CVE-2025-1734: Streams HTTP wrapper does not fail for headers with invalid name and no colon
Published Mar 13, 2025
·Updated
Fixed (Streams HTTP wrapper does not fail for headers without colon). (CVE-2025-1734)
Other sources
In PHP from 8.1. before 8.1.32, from 8.2. before 8.2.28, from 8.3. before 8.3.19, from 8.4. before 8.4.5, when receiving headers from HTTP server, the headers missing a colon (:) are treated as valid headers even though they are not. This may confuse applications into accepting invalid headers.
— Debian
Affected Software
9 affected componentsFixes available
PHP PHP<8.2.28
8.2.28
debian/php7.4<=7.4.33-1+deb11u5
7.4.33-1+deb11u8
debian/php8.2<=8.2.26-1~deb12u1
8.2.28-1~deb12u1
debian/php8.4
8.4.5-1
PHP PHP>=8.1.0<8.1.32
PHP PHP>=8.2.0<8.2.28
PHP PHP>=8.3.0<8.3.19
PHP PHP>=8.4.0<8.4.5
NetApp Ontap=9
Event History
Mar 13, 2025
CVE Published
via PHP·12:00 AM
Mar 30, 2025
CVE Published
via MITRE·05:43 AM
Data Sourced
via MITRE·05:43 AM
DescriptionWeakness
Data Sourced
via Red Hat·06:01 AM
DescriptionSeverityAffected Software
Data Sourced
via NVD·06:15 AM
DescriptionSeverityWeaknessAffected Software
Mar 31, 2025
Data Sourced
via Ubuntu·11:16 PM
RemedyDescriptionSeverityAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2025-1734?
CVE-2025-1734 has been classified as a moderate severity vulnerability.
2
How do I fix CVE-2025-1734?
To fix CVE-2025-1734, update PHP to version 8.3.19 or later.
3
What does CVE-2025-1734 affect?
CVE-2025-1734 affects PHP versions prior to 8.3.19.
4
Can CVE-2025-1734 lead to security issues in applications?
Yes, CVE-2025-1734 can lead to unexpected behaviors in applications if not addressed.
5
Is CVE-2025-1734 a known issue?
Yes, CVE-2025-1734 is a documented vulnerability in the PHP changelog.