# CVE-2011-1323: Denial of service in n/a

> Remote attackers can cause a denial of service and device reboot on Yamaha and NEC routers by sending crafted IP header options.

- **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:** 9 May 2011
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-2rcj-9v96-9vwg

## What is CVE-2011-1323?

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

### Official description

Yamaha RTX, RT, SRT, RTV, RTW, and RTA series routers with firmware 6.x through 10.x, and NEC IP38X series routers with firmware 6.x through 10.x, do not properly handle IP header options, which allows remote attackers to cause a denial of service (device reboot) via a crafted option that triggers access to an invalid memory location.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2011-1323?

It affects 52 products.


Products: Nec Ip38x\/1000, Nec Ip38x\/103, Nec Ip38x\/105, Nec Ip38x\/107e, Nec Ip38x\/1100, Nec Ip38x\/1200, Nec Ip38x\/140, Nec Ip38x\/1500, Nec Ip38x\/200, Nec Ip38x\/2000, Nec Ip38x\/250i, Nec Ip38x\/300, Nec Ip38x\/3000, Nec Ip38x\/52, Nec Ip38x\/55i, Nec Ip38x\/57i, Nec Ip38x\/58i, Nec Ip38x\/Sr100, Nec Ip38x\/V700, Yamaha Rt100i and 32 more.

## How do I fix CVE-2011-1323?

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

## Is CVE-2011-1323 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-1323 and fix it if it is affected.

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

## Sources

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

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