# CVE-2005-4275: Denial of service in n/a

> Remote attackers can crash the cable modem by sending a specific malformed IP packet, causing a denial of service.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/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:** 16 Dec 2005
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-v2cx-5pw8-pvw6

## What is CVE-2005-4275?

CVE-2005-4275 is a high-severity denial of service vulnerability in n/a, published on 16 Dec 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Scientific Atlanta DPX2100 Cable Modem allows remote attackers to cause a denial of service (device crash) via an IP packet with the same source and destination IPs and ports, and with the SYN flag set (aka LanD), as demonstrated using hping2.  NOTE: the provenance of this issue is unknown; the details are obtained solely from third party information.

## Which versions are affected by CVE-2005-4275?

It affects 1 product.


Products: Scientific Atlanta Dpx2100 Cable Modem.

## How do I fix CVE-2005-4275?

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

## Is CVE-2005-4275 being exploited?

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

Public exploit code:

- Scientific Atlanta DPX2100 Cable Modem - LanD Packet Denial of Service (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-4275 and fix it if it is affected.

What it is: CVE-2005-4275 is a high-severity denial of service vulnerability in n/a, published on 16 Dec 2005. 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-2005-4275 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-2005-4275/ (Markdown: https://insights.sbomify.com/CVE-2005-4275/index.md)
```

## Sources

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

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