protocol.c in the Apache HTTP Server 2.2.x through 2.2.21 does not properly restrict header information during…
No fixed version listed yet.Check the vendor advisory. References ↓
The protocol.c component of the Apache HTTP Server, in versions 2.2.x through 2.2.21, does not properly restrict header information when it builds Bad Request (400) error documents. An attacker can exploit this remotely by sending a long or malformed header in combination with crafted web script to obtain the values of HTTPOnly cookies.
Official description · CVE.org
protocol.c in the Apache HTTP Server 2.2.x through 2.2.21 does not properly restrict header information during construction of Bad Request (aka 400) error documents, which allows remote attackers to obtain the values of HTTPOnly cookies via vectors involving a (1) long or (2) malformed header in conjunction with crafted web script.
- Exploited
- Not confirmed
- 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.
Public exploit code (Exploit-DB) appeared 3 days after disclosure. No confirmed exploitation is recorded.
- Disclosedday 0
- Public exploit codeExploit-DB+3 days
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.
- Internal CVE Research9 Mar 2022