In Apache HTTP Server 2.4.32-2.4.39, when mod_remoteip was configured to use a trusted intermediary proxy server using…
No fixed version listed yet.Check the vendor advisory. References ↓
The flaw lies in Apache HTTP Server's mod_remoteip component in versions 2.4.32 through 2.4.39, where handling of the PROXY protocol header can lead to a stack buffer overflow or NULL pointer dereference. An attacker can exploit it only when mod_remoteip is configured to trust an intermediary proxy server using the PROXY protocol, by sending a specially crafted PROXY header through that trusted proxy, since untrusted HTTP clients cannot trigger it.
Official description · CVE.org
In Apache HTTP Server 2.4.32-2.4.39, when mod_remoteip was configured to use a trusted intermediary proxy server using the "PROXY" protocol, a specially crafted PROXY header could trigger a stack buffer overflow or NULL pointer deference. This vulnerability could only be triggered by a trusted proxy and not by untrusted HTTP clients.
- Exploited
- Yes, in VulnCheck KEV
- Reports
- 0
- Tactics
- 0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
First seen exploited 2 years after disclosure.
- Disclosedday 0
- First seen exploitedVulnCheck KEV evidence+2 yrs
Affected versions and fixes
as published in the CVE recordApache HTTP Server
Affected: 2.4.32 to 2.4.39
What security researchers reported
Not named in any threat report yetAlso mentioned in 1 community threat pulse (AlienVault OTX)
Weaker evidencePulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.