ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2010-0408

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 whic…

Published Mar 5, 2010 · catalog updated Jun 16, 2026 · http server

Last checked Nov 7, 2026. A connected source was read within the last 7 days.

Check this week

CVE-2010-0408 is not in CISA KEV. FIRST estimates a 20.89% chance of exploitation in the next 30 days. Check whether you run http server.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.

Same product and reporting

Severity
Medium5.0
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
20.89%
Remediation
Advisory link
Affected products
cpe apache/http server

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe apache/http server2.2
  • cpe apache/http server2.2.0
  • cpe apache/http server2.2.2
  • cpe apache/http server2.2.3
  • cpe apache/http server2.2.4
  • cpe apache/http server2.2.6

How to fix CVE-2010-0408

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

CVE-2010-0408 is not in CISA KEV. FIRST estimates a 20.89% chance of exploitation in the next 30 days. Check whether you run http server.

Which versions are affected?

Compare what you have installed with apache/http server 2.2; apache/http server 2.2.0; apache/http server 2.2.2; apache/http server 2.2.3. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 20.89%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Apache HTTP Server security

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Mar 5, 2010 · Monitored products — critical

    Detected

    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.

  2. Jun 16, 2026 · Monitored products — critical

    Updated

    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.

Sources

  • CVE.orgVulnerability recordCVE-2010-0408

    Official CVE identifier

    cve.org
  • Monitored products — criticalVendor advisoryCVE-2010-0408

    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.

    nvd.nist.gov

References

Freshness

Last verified in this catalog Nov 7, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • CVE.orgNov 4, 2026
  • Monitored products — criticalNov 4, 2026