# CVE-2008-5284: Integer overflow in n/a

> Remote attackers can crash the RadiusNT and RadiusX web server by sending an HTTP request with a negative Content-Length header, causing a denial of service.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Nov 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-h834-xm8f-qq56

## What is CVE-2008-5284?

CVE-2008-5284 is a critical vulnerability in n/a, published on 29 Nov 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The web server in IEA Software RadiusNT and RadiusX 5.1.38 and other versions before 5.1.44, Emerald 5.0.49 and other versions before 5.0.52, Air Marshal 2.0.4 and other versions before 2.0.8, and Radius test client (aka Radlogin) 4.0.20 and earlier, allows remote attackers to cause a denial of service (crash) via an HTTP Content-Length header with a negative value, which triggers a single byte overwrite of memory using a NULL terminator.  NOTE: some of these details are obtained from third party information.

Weakness: CWE-189

## Which versions are affected by CVE-2008-5284?

It affects 6 products.


Products: Iea Software Air Marshal, Iea Software Emerald, Iea Software Radius Test Client, Iea Software Radiusnt, Iea Software Radiusx, Iea Software Radlogin.

## How do I fix CVE-2008-5284?

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

## Is CVE-2008-5284 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-5284 exists.

Public exploit code:

- IEA Software (Multiple Products) - POST Denial of Service (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-5284 and fix it if it is affected.

What it is: CVE-2008-5284 is a critical vulnerability in n/a, published on 29 Nov 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-5284 exists.

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-2008-5284/ (Markdown: https://insights.sbomify.com/CVE-2008-5284/index.md)
```

## Sources

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

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