CVE-2024-11234 | Configuring a proxy in a stream context might allow for CRLF injection in URIs

Exp

In PHP versions 8.1.* before 8.1.31, 8.2.* before 8.2.26, 8.3.* before 8.3.14, when using streams with configured proxy and "request_fulluri" option, the URI is not properly sanitized which can lead to HTTP request smuggling and allow the attacker to use the proxy to perform arbitrary HTTP requests originating from the server, thus potentially gaining access to resources not normally available to the external user.

Published: 2024-11-24 Last update: 2025-11-03 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-11234 is rated High Exploit Risk (61.3/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 1.15%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2024-11234

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2024-11234

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-09 1.56% 1.15% -0.41%
2 2026-04-07 2.10% 1.56% -0.54%
3 2026-03-27 — 2.10% —

Full EPSS history (28 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-11234

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.8 3.1 MEDIUM
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 2.2 2.5 [email protected]
7.2 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 2.7 [email protected]

Weakness enumeration for CVE-2024-11234

OS Trackers for CVE-2024-11234

vendor priority summary link
alpine medium CVE-2024-11234: 1 source package rows (php83); 4 state rows across 4 repos (3.20-community, 3.21-community, 3.22-community, edge-community); fixed 4, open 0. https://security.alpinelinux.org/vuln/CVE-2024-11234
debian not yet assigned CVE-2024-11234 not yet assigned priority: Debian including 2 source packages (php7.4, php8.2), 2 status rows across 2 suites (bookworm, bullseye): resolved 2. https://security-tracker.debian.org/tracker/CVE-2024-11234
redhat medium — https://access.redhat.com/security/cve/CVE-2024-11234
suse medium CVE-2024-11234 severity moderate: SUSE including 389 source package names (8.2.26-47.4:apache2-mod_php8-8.2.26-150600.3.9.1, 8.2.26-47.4:php8-8.2.26-150600.3.9.1, …), 828 product×package rows across 20 product lines (Container bci/php, Container bci/php-apache, … (20 product lines)): Fixed 781, Known Not Affected 47. https://www.suse.com/security/cve/CVE-2024-11234/
ubuntu medium CVE-2024-11234 medium priority: Ubuntu including 6 source packages (php5, php7.0, php7.2, php7.4, php8.1, php8.3), 45 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 32, needs-triage 8, released 5. https://ubuntu.com/security/CVE-2024-11234

Affected software / configurations for CVE-2024-11234

Vendor Product Version Raw CPE
php php >= 8.1.0, < 8.1.31 cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
php php >= 8.2.0, < 8.2.26 cpe:2.3:a:php:php:*:*:*:*:*:*:*:*
php php >= 8.3.0, < 8.3.14 cpe:2.3:a:php:php:*:*:*:*:*:*:*:*

References for CVE-2024-11234

cvelogic Threat Intelligence