CVE-2010-0408

medium

Published 2010-03-05 · Modified 2026-04-29

💬 Discuss on Community ✚ Propose mitigation

CVSS v3

—

CVSS v4 NEW

—

not yet in upstream

VIR risk

5.0

Description

The ap_proxy_ajp_request function in mod_proxy_ajp.c in mod_proxy_ajp in the Apache HTTP Server 2.2.x before 2.2.15 does not properly handle certain situations in which a client sends no request body, which allows remote attackers to cause a denial of service (backend server outage) via a crafted request, related to use of a 500 error code instead of the appropriate 400 error code.

Predictions

Exploit likelihood

20%

Patch ETA

—

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No mitigations published for this CVE yet.

The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.

✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here with source_tier=community-verified.

OS impact

Debian Fixed 5 releases

Version	Status	Fixed in
trixie	Fixed	`2.2.15-1`
sid	Fixed	`2.2.15-1`
forky	Fixed	`2.2.15-1`
bullseye	Fixed	`2.2.15-1`
bookworm	Fixed	`2.2.15-1`

Application impact

Vendor	Product	Versions
apache	http_server	`2.2.2`
apache	http_server	`2.2.3`
apache	http_server	`2.2.4`
apache	http_server	`2.2`
apache	http_server	`2.2.6`
apache	http_server	`2.2.0`
apache	http_server	`2.2.8`
apache	http_server	`2.2.9`
apache	http_server	`2.2.11`
apache	http_server	`2.2.12`
apache	http_server	`2.2.13`
apache	http_server	`2.2.14`

References

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.