# CVE-2003-0450: Memory corruption in n/a

> Remote attackers can cause denial of service or execute arbitrary code via a buffer overflow in the Cistron RADIUS daemon.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Jun 2003
- **Updated:** 8 Aug 2024
- **Also known as:** DSA-321, GHSA-cw35-p78f-2qfc

## What is CVE-2003-0450?

CVE-2003-0450 is a high-severity memory corruption vulnerability in n/a, published on 20 Jun 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cistron RADIUS daemon (radiusd-cistron) 1.6.6 and earlier allows remote attackers to cause a denial of service and possibly execute arbitrary code via a large value in an NAS-Port attribute, which is interpreted as a negative number and causes a buffer overflow.

## Which versions are affected by CVE-2003-0450?

It affects 1 product.


Products: Cistron Radius Daemon.

## How do I fix CVE-2003-0450?

Apply the vendor's patch.

## Is CVE-2003-0450 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-0450 and fix it if it is affected.

What it is: CVE-2003-0450 is a high-severity memory corruption vulnerability in n/a, published on 20 Jun 2003. 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-2003-0450 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-2003-0450/ (Markdown: https://insights.sbomify.com/CVE-2003-0450/index.md)
```

## Sources

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

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