dbcve.org
Fwx120Hardware / appliance · Yamaha

CVE-2013-7310

MEDIUM · 5.4 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 →
59/100
Remediation priority · Elevated
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 Yamaha 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 in Yamaha routers fails to validate for duplicate Link State ID values in incoming Link State Advertisement (LSA) packets before processing them in the LSA database. This allows remote attackers to send crafted LSA packets with duplicate Link State IDs, potentially causing routing disruption (denial of service) or leaking sensitive routing information. This vulnerability is related to CVE-2013-0149, which involved similar OSPF implementation flaws in other vendors.

MitigationApply vendor-supplied firmware patches for Yamaha routers when available. Until patched, consider network segmentation to restrict OSPF traffic to trusted segments and implement OSPF MD5 authentication to prevent unauthorized LSA injection.

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
Fwx120Hardware / appliance
Affected:all versions
Rt105Hardware / appliance
Affected:all versions
Rt107eHardware / appliance
Affected:all versions
Rt140Hardware / appliance
Affected:all versions
Rt250iHardware / appliance
Affected:all versions
Rt300iHardware / appliance
Affected:all versions
Rtx1000Hardware / appliance
Affected:all versions
Rtx1100Hardware / 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
Adjacent
Complexity
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:A/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 router console or web interface and run the 'show environment' or 'show system' command, or check the device label. Confirm the model is one of: FWx120, RT105, RT107e, RT140, RT250i, RT300i, RTX1000, or RTX1100.
    Affected if The device is any of these eight Yamaha router models.
  2. Verify if OSPF is enabled
    Run the command 'show ip ospf' or 'show protocol' in the router console to check for OSPF configuration. Also check running config with 'show config' for any 'ospf' or 'router ospf' statements.
    Affected if OSPF protocol is actively enabled on the router.
  3. Check OSPF authentication configuration
    Run 'show ip ospf interface' to examine each OSPF-enabled interface. Look for authentication settings in the output. If using OSPF, verify that MD5 authentication is configured with 'show ospf auth' or inspect the interface configuration.
    Affected if OSPF is enabled but MD5 authentication is NOT configured on OSPF interfaces.
  4. Verify OSPF network exposure
    Review OSPF network statements and interface assignments with 'show ip ospf neighbor' to identify which networks participate in OSPF. Check if these networks are trusted or if OSPF is exposed to external/untrusted segments.
    Affected if OSPF is enabled and the network segment includes untrusted or external-facing networks.

If the device is any Yamaha model from FWx120 to RTX1100, OSPF is enabled, and OSPF lacks MD5 authentication or operates in an untrusted network segment, the environment is vulnerable to CVE-2013-7310.

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-supplied firmware patches for Yamaha routers when available. Until patched, consider network segmentation to restrict OSPF traffic to trusted segments and implement OSPF MD5 authentication to prevent unauthorized LSA injection.

Fix this in Fwx120 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-7310 — 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-7310 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