# CVE-2008-3208: Denial of service in n/a

> Remote attackers can cause a denial of service in Simple DNS Plus by sending multiple DNS reply packets.

- **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:** 18 Jul 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-827c-w44j-24gr

## What is CVE-2008-3208?

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

### Official description

Simple DNS Plus 4.1, 5.0, and possibly other versions before 5.1.101 allows remote attackers to cause a denial of service via multiple DNS reply packets.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Simpledns Simple Dns Plus.

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

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

## Is CVE-2008-3208 being exploited?

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

Public exploit code:

- Simple DNS Plus 5.0/4.1 - Remote Denial of Service (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-3208 is a medium-severity denial of service vulnerability in n/a, published on 18 Jul 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-3208 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-3208/ (Markdown: https://insights.sbomify.com/CVE-2008-3208/index.md)
```

## Sources

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

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