# CVE-2006-4523: Denial of service in n/a

> Remote attackers can crash 2Wire modems and routers by sending a GET request with a CRLF sequence, causing a denial of service.

- **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:** 1 Sep 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-c4cm-7xmj-gphj

## What is CVE-2006-4523?

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

### Official description

The web-based management interface in 2Wire, Inc. HomePortal and OfficePortal Series modems and routers allows remote attackers to cause a denial of service (crash) via a CRLF sequence in a GET request.

## Which versions are affected by CVE-2006-4523?

It affects 2 products.


Products: 2wire Inc Homeportal, 2wire Inc Officeportal.

## How do I fix CVE-2006-4523?

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

## Is CVE-2006-4523 being exploited?

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

Public exploit code:

- 2WIRE Modems/Routers - 'CRLF' Denial of Service (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-4523 and fix it if it is affected.

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

## Sources

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

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