CVE-2012-0053 is an information-disclosure vulnerability in Apache HTTP Server versions 2.2.0 through 2.2.21 and version 2.4.0. When constructing a default HTTP 400 Bad Request error response, the server can include insufficiently restricted request-header data. A malicious web script can induce a request containing a malformed or excessively long header and recover HttpOnly cookie values reflected in the resulting error document. The issue is relevant when the default 400 ErrorDocument is used.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Apache httpdにおけるHttpOnly Cookie関連の脆弱性で、非破壊的な挙動確認により脆弱性有無とおおよそのバージョン推定に使われる。Apache httpd 2.2.22以降で修正されたと説明されている。
An information disclosure vulnerability in Apache HTTP Server error responses that could expose HttpOnly cookies when no custom ErrorDocument is configured for HTTP 400 responses.
A medium-severity information-disclosure vulnerability in Apache HTTP Server 2.2.x through 2.2.21. Improper restriction of request-header information in generated HTTP 400 Bad Request documents could allow a remote attacker, using a crafted script and long or malformed header, to obtain HTTPOnly cookie values.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.