CVE-2011-3323
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 OSPFv3 implementation in ospf6d in Quagga before 0.99.19 allows remote attackers to cause a denial of service (out-of-bounds memory access and daemon crash) via a Link State Update message with an invalid IPv6 prefix length.
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 ospf6d daemon in Quagga versions before 0.99.19 contains an out-of-bounds memory access vulnerability in its OSPFv3 implementation. When processing a Link State Update message containing an invalid IPv6 prefix length, the daemon attempts to access memory outside the intended buffer bounds, causing a crash and resulting in denial of service.
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<= 0.99.18= 0.95= 0.96= 0.96.1= 0.96.2= 0.96.3= 0.96.4= 0.96.5= 0.97.0= 0.97.1= 0.97.2= 0.97.3CVSS 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
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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.
-
Check if ospf6d process is runningRun 'ps aux | grep ospf6d' or 'pgrep ospf6d' to see if the ospf6d daemon is activeAffected if ospf6d process is running and the system has not been patched to version 0.99.19 or later
-
Identify installed Quagga versionRun 'quagga -v' or 'ospf6d -v' to display version information, or check the package manager (dpkg -l quagga, rpm -q quagga)Affected if The installed version is 0.99.18 or earlier, or matches any of these: 0.95, 0.96, 0.96.1, 0.96.2, 0.96.3, 0.96.4, 0.96.5, 0.97.0, 0.97.1, 0.97.2, 0.97.3
-
Verify OSPFv3 is configuredExamine the Quagga ospf6d configuration file (commonly /etc/quagga/ospf6d.conf or similar) for any 'router ospf6' lines or OSPFv3-related interface configurationsAffected if OSPFv3 routing is enabled and ospf6d is actively processing OSPFv3 packets
-
Confirm ospf6d is enabled in Quagga daemon configurationCheck the Quagga daemon configuration file (typically /etc/quagga/daemons) to verify ospf6d is set to 'yes' or '1'Affected if ospf6d daemon is enabled and would process incoming OSPFv3 Link State Update messages
The system is affected if ospf6d is running with a Quagga version 0.99.18 or earlier (or one of the specific vulnerable versions listed) and OSPFv3 is configured, exposing the daemon to malformed OSPFv3 packets.
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 dataUpgrade Quagga to version 0.99.19 or later to obtain the patched ospf6d daemon, or implement network-level filtering to drop malformed OSPFv3 Link State Update packets with invalid prefix lengths before they reach affected routers.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.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 $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-3323 — 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-2011-3323 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