dbcve.org
QuaggaApplication

CVE-2010-2948

MEDIUM · 6.5 CVSS v2.0 Published 2010-09-10
Fix available
A fix is available. Upgrade to after 0.99.16 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Stack-based buffer overflow in the bgp_route_refresh_receive function in bgp_packet.c in bgpd in Quagga before 0.99.17 allows remote authenticated users to cause a denial of service (daemon crash) or possibly execute arbitrary code via a malformed Outbound Route Filtering (ORF) record in a BGP ROUTE-REFRESH (RR) message.

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

Stack-based buffer overflow in the bgp_route_refresh_receive function in bgp_packet.c in Quagga bgpd. The vulnerability triggers when processing malformed Outbound Route Filtering (ORF) records within BGP ROUTE-REFRESH messages, allowing authenticated remote attackers to crash the daemon or potentially execute arbitrary code.

MitigationUpgrade Quagga to version 0.99.17 or later. Until upgraded, restrict BGP peer access to trusted sources and implement BGP MD5 authentication between peers as defense-in-depth.

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
QuaggaApplication
Affected:<= 0.99.16= 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

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
Network
Complexity
Low
Authentication
Single
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:S/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. Verify Quagga bgpd is installed
    Run 'rpm -q quagga' or 'dpkg -l quagga' or check for /usr/sbin/bgpd binary
    Affected if Quagga package is not installed or bgpd binary does not exist - not affected
  2. Determine installed Quagga version
    Run 'bgpd -v' or 'rpm -q --qf "%{VERSION}\n" quagga' or check package manager
    Affected if Version is 0.99.16 or lower, OR one 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 - likely affected
  3. Confirm bgpd process is running
    Run 'ps aux | grep bgpd' or check if port 179 is listening with 'netstat -tlnp | grep 179'
    Affected if bgpd is not running - not currently vulnerable to network attack
  4. Check if BGP is configured with peers
    Inspect BGP configuration file (typically /etc/quagga/bgpd.conf or /etc/quagga/bgpd.conf) for 'neighbor' statements under router bgp context
    Affected if No BGP peers configured - reduced attack surface but version still matters if reachable
  5. Check if ORF capability is enabled
    Search BGP config for 'capability orf' or 'neighbor X capability orf' statements indicating Outbound Route Filtering is configured
    Affected if ORF is explicitly configured - this is the specific feature that triggers the vulnerability in bgp_route_refresh_receive

Environment is affected if running a vulnerable Quagga version (0.99.16 or lower, or any of the listed 0.9x versions) AND bgpd is actively running with BGP peers, with ORF capability being the specific trigger condition.

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
Upgrade available Upgrade to a release after 0.99.16
Interim mitigation

Upgrade Quagga to version 0.99.17 or later. Until upgraded, restrict BGP peer access to trusted sources and implement BGP MD5 authentication between peers as defense-in-depth.

Fix this in Quagga Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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