CVE-2010-0408

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. Limited direct impact.

Exploit odds

20.9% chance of exploitation in the next 30 days (EPSS). Higher than most.

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2010-03-05 16:30 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-16 23:16 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 20.9% in the next 30 days (EPSS).
• Severity: 5.0 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2010-03-05 16:30 UTC

Last modified

2026-06-16 23:16 UTC

Exploit probability

20.9% · EPSS, next 30 days

Record status

Modified

Affected

• Apache Http Server 2.2
• Apache Http Server 2.2.0
• Apache Http Server 2.2.2
• Apache Http Server 2.2.3
• Apache Http Server 2.2.4
• Apache Http Server 2.2.6
• Apache Http Server 2.2.8
• Apache Http Server 2.2.9

Attack profile CVSS 2.0 · 5.0

Attack vector

Network

Complexity

Low

Authentication

None

Confidentiality

None

Integrity

None

Availability

Partial

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2010-0408.md and follow it. Check whether this project is affected by CVE-2010-0408. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge