CVE-2013-7306
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 · uneditedThe OSPF implementation on Brocade 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 confidenceThe OSPF routing protocol implementation on Brocade routers fails to validate for duplicate Link State IDs when processing Link State Advertisement (LSA) packets. This allows remote attackers to send crafted LSA packets with duplicate Link State IDs to corrupt the LSA database, causing routing disruption (denial of service) or potentially extracting sensitive routing information.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Brocade router modelLog into the device and run the 'show version' or 'show chassis' command to confirm the exact model numberAffected if The model is one of: Adx, Bigiron Rx, Fastiron, Icx, Mlx, Netiron Cer, Netiron Ces, or Netiron Xmr
-
Check if OSPF is enabledRun 'show ip ospf' or 'show running-config | include ospf' to see if OSPF is configured and activeAffected if OSPF process is running and the router participates in OSPF routing
-
Verify OSPF MD5 authentication statusRun 'show ip ospf interface' or examine the OSPF configuration to check if MD5 authentication is configured on OSPF interfacesAffected if MD5 authentication is NOT configured on OSPF interfaces (the router accepts OSPF packets without authentication verification)
-
Check OSPF packet filtering at network boundariesInspect access control lists or firewall rules on border devices to determine if OSPF packets from external sources are being blockedAffected if OSPF traffic is not filtered and external OSPF packets can reach the vulnerable device
The environment is affected if the router is one of the listed Brocade models, OSPF is enabled, MD5 authentication is not configured, and OSPF packets from untrusted sources are not blocked at network boundaries.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate Brocade router firmware to vendor-provided patches addressing this OSPF vulnerability. If patches are unavailable, implement OSPF MD5 authentication on all OSPF adjacencies to prevent unauthorized LSA injection, and filter OSPF packets at network boundaries to block external OSPF traffic.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2013-7306 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-7306 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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