CVE-2011-3327
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 · uneditedHeap-based buffer overflow in the ecommunity_ecom2str function in bgp_ecommunity.c in bgpd in Quagga before 0.99.19 allows remote attackers to cause a denial of service (daemon crash) or possibly execute arbitrary code by sending a crafted BGP UPDATE message over IPv4.
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 confidenceHeap-based buffer overflow in the ecommunity_ecom2str function in bgp_ecommunity.c in Quagga's bgpd daemon. The vulnerability is triggered by processing a crafted BGP UPDATE message containing malformed extended community attributes, causing overflow on the heap and leading to daemon crash or potential arbitrary code execution.
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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/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.
-
Verify Quagga bgpd is installedRun 'rpm -q quagga' or 'dpkg -l quagga' or check for /usr/sbin/bgpd file existenceAffected if Quagga package or bgpd binary is present on the system
-
Check installed Quagga versionRun 'bgpd -v' or 'quagga -v' or 'rpm -qi quagga' to obtain the exact version numberAffected if Version is 0.99.18 or earlier, or matches any of: 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
-
Confirm bgpd daemon is runningRun 'ps aux | grep bgpd' or 'systemctl status bgpd' to check if the daemon is activeAffected if bgpd process is currently running
-
Check for BGP peer configurationInspect /etc/quagga/bgpd.conf or /etc/quagga/bgpd.conf for 'neighbor' statements under router bgp configurationAffected if BGP neighbors are configured, enabling processing of BGP UPDATE messages
-
Verify extended community attribute handlingCheck bgpd configuration for 'extended-community' in route-maps or BGP policy configurations that would trigger the vulnerable ecommunity_ecom2str code pathAffected if BGP extended community attributes are being processed or advertised
User is affected if Quagga bgpd is running a version 0.99.18 or earlier (or any version 0.95-0.97.3 listed) and accepts BGP connections from untrusted peers that could send malformed extended community attributes.
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 which contains the fix. If immediate upgrade is not feasible, restrict BGP peer access through ACLs or network segmentation to limit exposure to untrusted BGP neighbors.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,864.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-3327 — 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-3327 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