# CVE-2013-7314: Denial of service in n/a

> Remote attackers can cause routing disruption or leak sensitive data on NEC routers by sending crafted OSPF LSA packets with duplicate IDs.

- **Severity:** Medium 6.8 (`AV:N/AC:M/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:** No
- **Published:** 23 Jan 2014
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-r3f3-f3vp-h6w9

## What is CVE-2013-7314?

CVE-2013-7314 is a medium-severity denial of service vulnerability in n/a, published on 23 Jan 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The OSPF implementation on NEC IP38X, IX1000, IX2000, and IX3000 routers does not consider the possibility of duplicate Link State ID values in Link State Advertisement (LSA) packets before performing operations on the LSA database, which allows remote attackers to cause a denial of service (routing disruption) or obtain sensitive packet information via a crafted LSA packet, a related issue to CVE-2013-0149.

## Which versions are affected by CVE-2013-7314?

It affects 12 products.


Products: Nec Ip38x 1000, Nec Ip38x 105, Nec Ip38x 107e, Nec Ip38x 1100, Nec Ip38x 1200, Nec Ip38x 140, Nec Ip38x 1500, Nec Ip38x 2000, Nec Ip38x 250i, Nec Ip38x 300, Nec Ip38x 3000, Nec Ip38x 810.

## How do I fix CVE-2013-7314?

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

## Is CVE-2013-7314 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-7314 and fix it if it is affected.

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

## Sources

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

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