CVE-2009-2620

UNRATEDCVSS · not yet scoredWeaponized
—
EchelonGraph verdictPlan mitigationWithin your standard update timelines — no confirmed exploitation yet.
  • Public exploit code is available (Exploit-DB, marked verified by Exploit-DB)
CISA-KEV: Not listedEPSS PROB: 8.6%CVSS v2: —Exploit: Exploit-DB (verified)Exposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

src/remote/server.cpp in fbserver.exe in Firebird SQL 1.5 before 1.5.6, 2.0 before 2.0.6, 2.1 before 2.1.3, and 2.5 before 2.5 Beta 2 allows remote attackers to cause a denial of service (daemon crash) via a malformed op_connect_request message that triggers an infinite loop or NULL pointer dereference.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
8.6%
EPSS %ILE
94th
KEV
Not listed

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 29, 2009

Last Modified

August 7, 2024

References (7)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 16× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-12 01:53 UTCEG score recompute
  2. 2026-10-11 13:38 UTCEPSS rescoreEPSS 8.6% · 94th percentile
  3. 2026-10-10 19:54 UTCEPSS rescoreEPSS 8.6% · 94th percentile
  4. 2026-10-09 20:00 UTCEPSS rescoreEPSS 8.6% · 94th percentile
  5. 2026-10-08 16:33 UTCEPSS rescoreEPSS 8.6% · 94th percentile
  6. 2026-10-07 23:37 UTCEPSS rescoreEPSS 8.6% · 94th percentile
  7. 2026-10-06 15:09 UTCEPSS rescoreEPSS 8.6% · 94th percentile
  8. 2026-10-05 17:37 UTCEPSS rescoreEPSS 8.6% · 94th percentile
  9. 2026-09-30 14:58 UTCEPSS rescoreEPSS 8.6% · 94th percentile
  10. 2026-09-29 07:59 UTCEG score recompute
  11. 2026-09-27 13:39 UTCEPSS rescoreEPSS 8.6% · 94th percentile
  12. 2026-09-26 15:52 UTCEPSS rescoreEPSS 8.6% · 94th percentile
  13. 2026-09-24 13:57 UTCEPSS rescoreEPSS 8.6% · 94th percentile
  14. 2026-09-17 19:20 UTCEPSS rescoreEPSS 8.6% · 94th percentile
  15. 2026-09-15 03:04 UTCEPSS rescoreEPSS 8.6% · 94th percentile
  16. 2026-09-12 14:54 UTCEPSS rescoreEPSS 8.6% · 94th percentile
  17. 2026-09-10 09:24 UTCEPSS rescoreEPSS 8.6% · 94th percentile
  18. 2026-09-06 13:41 UTCEPSS rescoreEPSS 8.6% · 94th percentile
  19. 2026-09-05 15:22 UTCEPSS rescoreEPSS 8.6% · 94th percentile
  20. 2026-09-04 13:55 UTCEPSS rescoreEPSS 8.6% · 94th percentile
  21. 2026-08-28 21:34 UTCEPSS rescoreEPSS 8.6% · 94th percentile
  22. 2026-08-27 14:19 UTCEPSS rescoreEPSS 8.6% · 94th percentile
  23. 2026-08-25 13:43 UTCEPSS rescoreEPSS 8.6% · 94th percentile
  24. 2026-08-19 16:58 UTCEPSS rescoreEPSS 8.6% · 94th percentile
  25. 2026-08-15 01:24 UTCEPSS rescoreEPSS 8.6% · 94th percentile
Show 8 more
  1. 2026-08-09 13:41 UTCEPSS rescoreEPSS 8.6% · 94th percentile
  2. 2026-08-08 16:31 UTCEPSS rescoreEPSS 8.6% · 94th percentile
  3. 2026-08-06 13:41 UTCEPSS rescoreEPSS 8.6% · 94th percentile
  4. 2026-08-03 10:28 UTCEPSS rescoreEPSS 8.6% · 94th percentile
  5. 2026-07-30 16:22 UTCEPSS rescoreEPSS 8.6% · 94th percentile
  6. 2026-07-30 01:26 UTCEPSS rescoreEPSS 8.6% · 94th percentile
  7. 2026-07-27 12:57 UTCEG score recompute
  8. 2026-07-27 12:57 UTCGHSA enrichmentGHSA-rp94-92gp-7q47

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 Exploit-DB entry). No release with the fix is confirmed, so defenders should restrict or isolate affected systems accordingly until one is applied.

  • Exploit-DBEDB-9295✓ verified
    Published Jul 28, 2009

    Firebird SQL - op_connect_request main listener shutdown

    Open source ↗

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2009-2620?
CVE-2009-2620 is a vulnerability whose severity is not yet rated; its CVE record was published on July 29, 2009. src/remote/server.cpp in fbserver.exe in Firebird SQL 1.5 before 1.5.6, 2.0 before 2.0.6, 2.1 before 2.1.3, and 2.5 before 2.5 Beta 2 allows remote attackers to cause a denial of service (daemon crash) via a malformed opconnectrequest message that triggers an infinite loop or NULL pointer…
When was CVE-2009-2620 made public?
CVE-2009-2620 was made public on July 28, 2009: that is the date its CVE record's CNA, MITRE Corporation, gives for when the vulnerability was made public. The CVE record itself was published on July 29, 2009. EchelonGraph's copy of the record carries a last-modified date of August 7, 2024; the record at its source may have been updated since.
Is CVE-2009-2620 actively exploited?
CVE-2009-2620 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: Exploit-DB marks a public exploit for it as verified. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 8.6% probability of exploitation in the next 30 days (94th percentile of EPSS-scored CVEs).
How do I remediate CVE-2009-2620?
A fix for CVE-2009-2620 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2009-2620

Explore →

Is Your Infrastructure Affected by CVE-2009-2620?

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

Book a Demo →Browse All CVEs