CVE-2006-2224

NONECVSS 0.0Trending — 5 sources updated this weekWeaponized

0.0

RIPd in Quagga 0.98 and 0.99 before 20060503 does not properly enforce RIPv2 authentication requirements, which allows remote attackers to modify routing state via RIPv1 RESPONSE packets.

CVSS v3: —
EG Score: 0.0(none)
EPSS: 95.6%
KEV: Not listed

Published

May 5, 2006

Last Modified

April 16, 2026

References (46)

cve@mitreftp://patches.sgi.com/support/free/security/advisories/20060602-01-U.asc
cve@mitrehttp://bugzilla.quagga.net/show_bug.cgi?id=262
cve@mitrehttp://secunia.com/advisories/19910
cve@mitrehttp://secunia.com/advisories/20137
cve@mitrehttp://secunia.com/advisories/20138
cve@mitrehttp://secunia.com/advisories/20221
cve@mitrehttp://secunia.com/advisories/20420
cve@mitrehttp://secunia.com/advisories/20421
cve@mitrehttp://secunia.com/advisories/20782
cve@mitrehttp://secunia.com/advisories/21159
cve@mitrehttp://securitytracker.com/id?1016204
cve@mitrehttp://www.debian.org/security/2006/dsa-1059
cve@mitrehttp://www.gentoo.org/security/en/glsa/glsa-200605-15.xml
cve@mitrehttp://www.novell.com/linux/security/advisories/2006_17_sr.html
cve@mitrehttp://www.osvdb.org/25225

Patch Availability(4)

Vendor / Ecosystem	Fixed in / Patch	Released	Source
ubuntu	quagga () @ breezy	2026-05-31	ubuntu
redhat	quagga-0:0.98.3-2.4E	2006-06-01	redhat
redhat	patch	2006-06-01	redhat
debian:10	quagga @ 0.99.3-2	—	osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-287Improper Authentication

All Vendor Advisories

(3)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 15× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:10 UTCepss_batch
2026-06-02 20:10 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 08:47 UTCEG score recompute
2026-05-31 08:47 UTCVendor advisory
2026-05-31 08:47 UTCGHSA enrichment
2026-05-31 00:13 UTCepss_batch
2026-05-31 00:13 UTCepss_batch
2026-05-31 00:13 UTCepss_batch
2026-05-29 13:40 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-27 15:05 UTCOSV refresh
2026-05-27 13:37 UTCepss_batch
2026-05-27 13:37 UTCepss_batch
2026-05-26 07:16 UTCepss_batch
2026-05-26 07:16 UTCepss_batch
2026-05-24 16:42 UTCepss_batch
2026-05-22 21:15 UTCepss_batch
2026-05-22 21:15 UTCepss_batch

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

Exploit-DBEDB-27802✓ verified
First seen May 3, 2006
Quagga Routing Software Suite 0.9x - RIPd RIPv1 RESPONSE Packet Route Injection
Open source ↗

Frequently asked(4)

What is CVE-2006-2224?

CVE-2006-2224 is a none vulnerability published on May 5, 2006. RIPd in Quagga 0.98 and 0.99 before 20060503 does not properly enforce RIPv2 authentication requirements, which allows remote attackers to modify routing state via RIPv1 RESPONSE packets.

When was CVE-2006-2224 disclosed?

CVE-2006-2224 was first published in the National Vulnerability Database on May 5, 2006, with the most recent update on April 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2006-2224 actively exploited?

CVE-2006-2224 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 95.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

How do I remediate CVE-2006-2224?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2006-2224, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2006-2224

Explore →

Is Your Infrastructure Affected by CVE-2006-2224?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

Vendor / Ecosystem

Fixed in / Patch

Released

Source

ubuntu

quagga () @ breezy

2026-05-31

ubuntu

redhat

quagga-0:0.98.3-2.4E

2006-06-01

redhat

patch

2006-06-01

redhat

debian:10

quagga @ 0.99.3-2

—

osv

Frequently asked(4)

What is CVE-2006-2224?

When was CVE-2006-2224 disclosed?

Is CVE-2006-2224 actively exploited?

How do I remediate CVE-2006-2224?

CVE-2006-2224

Published

Last Modified

References (46)

Patch Availability(4)

Weakness Classification(1)

All Vendor Advisories

Data Freshness Timeline

Publicly available exploits

Frequently asked(4)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2006-2224?

CVE-2006-2224

Published

Last Modified

References (46)

Patch Availability(4)

Weakness Classification(1)

All Vendor Advisories

Data Freshness Timeline

Publicly available exploits

Frequently asked(4)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2006-2224?

Same product

Same vendor

Same CWE

CVE-2006-2224

📅 Published

🔄 Last Modified

🔗 References (46)

Patch Availability(4)

Weakness Classification(1)

All Vendor Advisories

Data Freshness Timeline

Publicly available exploits

❓ Frequently asked(4)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2006-2224?

CVE-2006-2224

📅 Published

🔄 Last Modified

🔗 References (46)

Patch Availability(4)

Weakness Classification(1)

All Vendor Advisories

Data Freshness Timeline

Publicly available exploits

❓ Frequently asked(4)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2006-2224?

🔗 Related CVEs(same product + same vendor + same CWE)

Same product

Same vendor

Same CWE

Published

Last Modified

References (46)

Frequently asked(4)

Published

Last Modified

References (46)

Frequently asked(4)

Related CVEs(same product + same vendor + same CWE)