CVE-2010-1674
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 extended-community parser in bgpd in Quagga before 0.99.18 allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) via a malformed Extended Communities attribute.
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 confidenceA NULL pointer dereference vulnerability exists in the extended-community parser of bgpd in Quagga routing software before version 0.99.18. A remote attacker can send a specially crafted malformed Extended Communities attribute in a BGP message, causing the bgpd daemon to crash due to the NULL pointer dereference.
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.17= 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.
-
Identify if Quagga bgpd is installedRun 'bgpd --version' or check your package manager for quagga package (e.g., dpkg -l | grep quagga, rpm -qa | grep quagga)Affected if Quagga bgpd is present on the system
-
Determine the installed Quagga versionCompare the version output from 'bgpd --version' to the affected ranges: Quagga versions <= 0.99.17, or specifically 0.95, 0.96, 0.96.1-0.96.5, 0.97.0-0.97.3Affected if The installed version is 0.99.17 or lower, or matches any of the specific affected versions listed (0.95, 0.96.x, 0.97.x)
-
Verify if bgpd daemon is runningCheck process list: 'ps aux | grep bgpd' or 'systemctl status bgpd'Affected if The bgpd process is actively running and accepting BGP connections
-
Confirm BGP peers are configuredInspect bgpd configuration (typically in /etc/quagga/bgpd.conf or via 'vtysh -c "show running"') and look for 'neighbor' statements under BGP configurationAffected if The bgpd configuration has configured BGP neighbors or peer groups, creating an attack surface for remote malformed Extended Communities attributes
You are affected if Quagga bgpd is running with a version at or below 0.99.17 (or matching 0.95/0.96.x/0.97.x) and has BGP peers configured, allowing remote attackers to send malformed Extended Communities that trigger the NULL pointer dereference crash.
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.18 or later to obtain the patch for this vulnerability. Additionally, implement BGP peering filtering and network segmentation to limit exposure to untrusted BGP peers.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-1674 — 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-2010-1674 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