CVE-2006-2224

NONECVSS 0.0Weaponized
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 10%CVSS: —Exploit: NoneExposed: 0

A fix is available — apply it.

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.2%
KEV
Not listed

Published

May 5, 2006

Last Modified

April 16, 2026

References (46)

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuquagga () @ breezy2026-05-31ubuntu
redhatquagga-0:0.98.3-2.4E2006-06-01redhat
redhatpatch2006-06-01redhat
debian:10quagga @ 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.

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 3× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-04 06:26 UTCEPSS rescore
  2. 2026-07-02 14:00 UTCEPSS rescore
  3. 2026-07-01 15:01 UTCEPSS rescore
  4. 2026-06-29 14:02 UTCEPSS rescore
  5. 2026-06-29 14:02 UTCEPSS rescore
  6. 2026-06-27 03:04 UTCEPSS rescore
  7. 2026-06-25 13:46 UTCEPSS rescore
  8. 2026-06-24 14:01 UTCEPSS rescore
  9. 2026-06-24 14:01 UTCEPSS rescore
  10. 2026-06-23 21:29 UTCEPSS rescore
  11. 2026-06-23 21:29 UTCEPSS rescore
  12. 2026-06-22 14:22 UTCEPSS rescore
  13. 2026-06-21 01:56 UTCEPSS rescore
  14. 2026-06-20 10:42 UTCOSV refresh
  15. 2026-06-19 19:22 UTCEPSS rescore
  16. 2026-06-19 19:22 UTCEPSS rescore
  17. 2026-06-18 17:49 UTCEPSS rescore
  18. 2026-06-18 17:49 UTCEPSS rescore
  19. 2026-06-17 17:49 UTCEPSS rescore
  20. 2026-06-17 17:49 UTCEPSS rescore
  21. 2026-06-16 17:49 UTCEPSS rescore
  22. 2026-06-16 17:49 UTCEPSS rescore
  23. 2026-06-15 17:44 UTCEPSS rescore
  24. 2026-06-14 23:13 UTCEPSS rescore
  25. 2026-06-13 22:56 UTCEPSS rescore
Show 36 more
  1. 2026-06-12 23:08 UTCEPSS rescore
  2. 2026-06-11 13:55 UTCEPSS rescore
  3. 2026-06-10 22:14 UTCEPSS rescore
  4. 2026-06-10 13:17 UTCEPSS rescore
  5. 2026-06-07 15:21 UTCEPSS rescore
  6. 2026-06-06 13:44 UTCEPSS rescore
  7. 2026-06-06 13:44 UTCEPSS rescore
  8. 2026-06-05 22:43 UTCEPSS rescore
  9. 2026-06-04 13:09 UTCEPSS rescore
  10. 2026-06-04 13:09 UTCEPSS rescore
  11. 2026-06-02 20:10 UTCEPSS rescore
  12. 2026-06-02 20:10 UTCEPSS rescore
  13. 2026-05-31 22:28 UTCEPSS rescore
  14. 2026-05-31 08:47 UTCEG score recompute
  15. 2026-05-31 08:47 UTCVendor advisory
  16. 2026-05-31 08:47 UTCGHSA enrichment
  17. 2026-05-31 00:13 UTCEPSS rescore
  18. 2026-05-31 00:13 UTCEPSS rescore
  19. 2026-05-31 00:13 UTCEPSS rescore
  20. 2026-05-29 13:40 UTCEPSS rescore
  21. 2026-05-28 13:42 UTCEPSS rescore
  22. 2026-05-28 13:42 UTCEPSS rescore
  23. 2026-05-27 15:05 UTCOSV refresh
  24. 2026-05-27 13:37 UTCEPSS rescore
  25. 2026-05-27 13:37 UTCEPSS rescore
  26. 2026-05-26 07:16 UTCEPSS rescore
  27. 2026-05-26 07:16 UTCEPSS rescore
  28. 2026-05-24 16:42 UTCEPSS rescore
  29. 2026-05-22 21:15 UTCEPSS rescore
  30. 2026-05-22 21:15 UTCEPSS rescore
  31. 2026-05-21 22:38 UTCEPSS rescore
  32. 2026-05-20 22:36 UTCEPSS rescore
  33. 2026-05-20 22:36 UTCEPSS rescore
  34. 2026-05-20 11:20 UTCEPSS rescore
  35. 2026-05-20 11:20 UTCEPSS rescore
  36. 2026-05-18 21:29 UTCEPSS rescore

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 ↗

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

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.2% 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

Explore the affected products and dependency analysis for 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