CVE-2012-0053

CVE-2012-0053

Published · Updated

45Vexday Risk Score

No sign of exploitation. It has a public proof of concept.

ssvc Attendepss 82%
from disclosure to weapon3 days
Published on NVDJan 28
1st PoC+3d
exploitation probability
82%top 1% of all CVEs
observed exploitation
nono source reports it
1 public exploit(s)
What the vendors declare (VEX)

Official vendor statements in CSAF/VEX format: whether their product is affected, already fixed, or ruled out — and why. These are the vendor's assertions, not Vexday's judgment.

Affected
2 products
Red Hat Directory Server 8 · Red Hat Enterprise Linux 4
workaround: As noted in the original reporter's advisory (see comment #5), this issue can be mitigated by using a custom ErrorDocument setting, such as: ErrorDocument 400 "Bad Request" http://httpd.apache.org/docs/2.2/mod/core.html#errordocument It should be…
Fixed
12 products (267 components)
RHEL Desktop Workstation (v. 5 client) · Red Hat Enterprise Linux (v. 5 server) · Red Hat Enterprise Linux Desktop (v. 5 client) · Red Hat Enterprise Linux Desktop (v. 6) · Red Hat Enterprise Linux Desktop Optional (v. 6) · and others 7
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.
Affected products
n/a · n/a
⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.