QuaggaApplication

CVE-2007-1995

MEDIUM · 6.3 CVSS v2.0 Published 2007-04-12

Fix available

A fix is available. Upgrade to after 0.98.6 or later.

See remediation →

69/100

Remediation priority · Elevated

Remotely reachable Zero-click

Official description

NVD · unedited

bgpd/bgp_attr.c in Quagga 0.98.6 and earlier, and 0.99.6 and earlier 0.99 versions, does not validate length values in the MP_REACH_NLRI and MP_UNREACH_NLRI attributes, which allows remote attackers to cause a denial of service (daemon crash or exit) via crafted UPDATE messages that trigger an assertion error or out of bounds read.

Technical summary

dbcve analysis · high confidence

The BGP daemon (bgpd) in Quagga versions 0.98.6 and earlier, and 0.99.6 and earlier, fails to validate length fields in the MP_REACH_NLRI and MP_UNREACH_NLRI attributes during BGP UPDATE message processing. This allows remote attackers sending crafted BGP UPDATE messages to trigger assertion failures or out-of-bounds memory reads, causing the daemon to crash or exit.

MitigationUpgrade Quagga to version 0.98.7, 0.99.7, or later which contain the length validation fix. As an interim measure, consider filtering unknown or suspicious BGP UPDATE messages at network edge devices.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

QuaggaApplication

Affected:<= 0.98.6= 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

From the vector

Attack vector: Network
Complexity: M
Authentication: Single
Confidentiality: None
Integrity: None
Availability: Complete

AV:N/AC:M/Au:S/C:N/I:N/A:C

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify installed Quagga package version

Run 'rpm -q quagga' for RHEL/CentOS, 'dpkg -l quagga' for Debian/Ubuntu, or 'quagga -v' to display version information

Affected if The reported version is 0.98.6 or earlier, or 0.99.6 or earlier, or one of the specific affected versions (0.95, 0.96.x, 0.97.x series)
Locate and verify bgpd binary version

Run 'bgpd -v' or check the binary at /usr/sbin/bgpd with 'file /usr/sbin/bgpd' and compare version strings using 'strings /usr/sbin/bgpd | grep -i version'

Affected if The binary version matches the vulnerable Quagga version ranges listed above
Confirm bgpd process is running

Run 'ps aux | grep bgpd' or check for the bgpd daemon process. Also verify port 179 is listening with 'netstat -tlnp | grep 179' or 'ss -tlnp | grep 179'

Affected if The bgpd process is actively running and BGP port 179 is in LISTEN state, making the service exposed to incoming BGP UPDATE messages
Check for BGP peer connections

Use 'vtysh -e "show ip bgp summary"' or access the bgpd telnet/VTY interface on port 2605 to view active BGP peers

Affected if There are established BGP peer connections from untrusted or external networks, indicating potential attack vector exposure
Audit BGP UPDATE message handling

Enable BGP debug logging via 'vtysh -e "debug bgp updates"' or inspect system logs (/var/log/bgpd.log or /var/log/messages) for recent BGP UPDATE processing activity

Affected if The system is logging or processing BGP UPDATE messages without evidence of length validation fixes applied to the installed version

A system is affected if it runs any Quagga version 0.98.6 or earlier, or 0.99.6 or earlier, with the bgpd daemon running and accepting BGP peer connections.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Upgrade available Upgrade to a release after 0.98.6

Interim mitigation

Upgrade Quagga to version 0.98.7, 0.99.7, or later which contain the length validation fix. As an interim measure, consider filtering unknown or suspicious BGP UPDATE messages at network edge devices.

Fix this in Quagga Scoped from the published advisory

Consultation4.0 h
Implementation8.0 h
Testing8.0 h
Review / QA4.0 h

24.0 hours of engineering $4,160

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-1995 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2007-1995?

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.

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

At a glance

A fix existsUpgrade to after 0.98.6 or later

Severity 6.3 Medium

Exploit likelihood EPSS, next 30 days 1.7%

Affects: Quagga

Remediation

Need this fixed?

Fix this in Quagga 24 hrs · Moderate

Typical engagement from $4,160

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2007-1995 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References