# CVE-2009-2299: Denial of service in n/a

> Remote attackers can cause denial of service via memory consumption by sending HTTP requests with large Content-Length headers but no data.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jul 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-23f2-7h54-3w8p

## What is CVE-2009-2299?

CVE-2009-2299 is a medium-severity denial of service vulnerability in n/a, published on 2 Jul 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Artofdefence Hyperguard Web Application Firewall (WAF) module before 2.5.5-11635, 3.0 before 3.0.3-11636, and 3.1 before 3.1.1-11637, a module for the Apache HTTP Server, allows remote attackers to cause a denial of service (memory consumption) via an HTTP request with a large Content-Length value but no POST data.

## Which versions are affected by CVE-2009-2299?

It affects 1 product.


Products: Hyperguard Web Application Firewall Project Hyperguard Web Application Firewall.

## How do I fix CVE-2009-2299?

No fix has been published for CVE-2009-2299 yet. Limit exposure of the affected software until one is available.

## Is CVE-2009-2299 being exploited?

There is no known exploitation of CVE-2009-2299 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-2299 and fix it if it is affected.

What it is: CVE-2009-2299 is a medium-severity denial of service vulnerability in n/a, published on 2 Jul 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2009-2299 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2009-2299/ (Markdown: https://insights.sbomify.com/CVE-2009-2299/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2009-2299
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2009-2299
- OSV: https://osv.dev/vulnerability/CVE-2009-2299

---
From sbomify Insights: https://insights.sbomify.com/CVE-2009-2299/
Summaries are generated and may contain mistakes; the official description above is the record.