dbcve.org
Ip38x 1000Hardware / appliance · Nec

CVE-2013-7314

MEDIUM · 6.8 CVSS v2.0 Published 2014-01-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The OSPF implementation on NEC IP38X, IX1000, IX2000, and IX3000 routers fails to validate for duplicate Link State ID values in incoming LSA packets before database operations. Attackers can send crafted LSA packets with duplicate Link State IDs to cause routing disruption (DoS) or potentially extract sensitive routing information from the OSPF database.

MitigationApply vendor firmware updates when available. Until then, enforce OSPF message authentication (MD5 or HMAC) to prevent injection of malicious LSA packets, and implement network segmentation to limit attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ip38x 1000Hardware / appliance
Affected:all versions
Ip38x 105Hardware / appliance
Affected:all versions
Ip38x 107eHardware / appliance
Affected:all versions
Ip38x 1100Hardware / appliance
Affected:all versions
Ip38x 1200Hardware / appliance
Affected:all versions
Ip38x 140Hardware / appliance
Affected:all versions
Ip38x 1500Hardware / appliance
Affected:all versions
Ip38x 2000Hardware / appliance
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:N/C:P/I:P/A:P

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the router model
    Access the device CLI or web interface and run 'show system' or check the device label/hardware sticker to confirm the exact model number (e.g., NEC Ip38x 1000, IX1000, IX2000, IX3000)
    Affected if The model is any of: Nec Ip38x 1000, Ip38x 105, Ip38x 107e, Ip38x 1100, Ip38x 1200, Ip38x 140, Ip38x 1500, Ip38x 2000, IX1000, IX2000, or IX3000
  2. Confirm OSPF protocol is enabled
    In the device CLI, run 'show ip ospf' or check the OSPF configuration via 'show running-config' to verify OSPF process is active
    Affected if OSPF is enabled and the router is participating in OSPF routing
  3. Verify OSPF interface participation
    Run 'show ip ospf interface' to list all interfaces where OSPF is enabled and active
    Affected if Any interface has OSPF enabled, making the device vulnerable to malformed LSA packets
  4. Check OSPF authentication configuration
    Run 'show ip ospf interface' and look for 'Authentication' field, or inspect the OSPF configuration for 'ip ospf authentication' settings on each OSPF-enabled interface
    Affected if OSPF authentication is NOT configured (null/authentication disabled), meaning the device accepts unauthenticated OSPF packets
  5. Review OSPF database for anomalies
    Run 'show ip ospf database' to display the Link State Database; look for duplicate Link State IDs or unexpected LSA types that may indicate exploitation attempts
    Affected if Duplicate Link State IDs appear in the OSPF database, indicating possible exploitation of this vulnerability

If the device is a NEC IP38X, IX1000, IX2000, or IX3000 router with OSPF enabled and OSPF authentication is not configured, the environment is affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware updates when available. Until then, enforce OSPF message authentication (MD5 or HMAC) to prevent injection of malicious LSA packets, and implement network segmentation to limit attack surface.

Fix this in Ip38x 1000 Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-7314 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-7314 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data