CVE-2017-11509

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2022-05-13. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 6%CVSS: 8.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

An authenticated remote attacker can execute arbitrary code in Firebird SQL Server versions 2.5.7 and 3.0.2 by executing a malformed SQL statement.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
47(Track)
EG Risk 47/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation6% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
6%
EPSS %ILE
93%
KEV
Not listed

Published

March 28, 2018

Last Modified

November 21, 2024

Advisory Details (4)

Auto-updated Jul 26, 2026
🔬 Proof of concept available. Patch available.
generic🟡 PoC Available

[R1] Firebird fbudf Module Authenticated Remote Code Execution - Research Advisory | Tenable®

https://www.tenable.com/security/research/tra-2017-36
generic Patch Available

[SECURITY] [DLA 2824-1] firebird3.0 security update

https://lists.debian.org/debian-lts-announce/2021/11/msg00018.html
generic Patch Available

[SECURITY] [DLA 2129-1] firebird2.5 security update

https://lists.debian.org/debian-lts-announce/2020/02/msg00036.html
generic Patch Available

[SECURITY] [DLA 1374-1] firebird2.5 security update

https://lists.debian.org/debian-lts-announce/2018/05/msg00005.html

Affected Packages

(7 across 7 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
firebird3.0—3.0.3.32900.ds4-3—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
firebird3.0—3.0.3.32900.ds4-3—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
firebird3.0—3.0.3.32900.ds4-3—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
firebird3.0—3.0.3.32900.ds4-3—
Debian:7(1)
PackageVulnerable rangeFixed inDependents
firebird2.52.5.2.26540.ds4-1~deb7u1, 2.5.2.26540.ds4-1~deb7u2, 2.5.2.26540.ds4-1~deb7u3, 2.5.2~svn+54698.ds4-32.5.2.26540.ds4-1~deb7u4—
Debian:8(1)
PackageVulnerable rangeFixed inDependents
firebird2.52.5.3.26778.ds4-5, 2.5.3.26778.ds4-5+deb8u12.5.3.26778.ds4-5+deb8u2—
Debian:9(1)
PackageVulnerable rangeFixed inDependents
firebird3.03.0.1.32609.ds4-143.0.1.32609.ds4-14+deb9u1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 23× 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.

Showing the most recent 100 of 124 total refreshes for this CVE.

  1. 2026-09-07 15:56 UTCEPSS rescore
  2. 2026-09-04 13:56 UTCEPSS rescore
  3. 2026-09-04 05:01 UTCEPSS rescore
  4. 2026-09-02 14:07 UTCEPSS rescore
  5. 2026-09-01 13:48 UTCEPSS rescore
  6. 2026-09-01 03:31 UTCEPSS rescore
  7. 2026-08-31 16:34 UTCOSV refresh
  8. 2026-08-30 19:13 UTCEPSS rescore
  9. 2026-08-28 21:36 UTCEPSS rescore
  10. 2026-08-27 14:20 UTCEPSS rescore
  11. 2026-08-26 14:41 UTCEPSS rescore
  12. 2026-08-25 13:44 UTCEPSS rescore
  13. 2026-08-24 14:10 UTCEPSS rescore
  14. 2026-08-21 23:44 UTCEPSS rescore
  15. 2026-08-20 22:50 UTCEPSS rescore
  16. 2026-08-19 16:59 UTCEPSS rescore
  17. 2026-08-18 13:43 UTCEPSS rescore
  18. 2026-08-16 14:51 UTCEPSS rescore
  19. 2026-08-16 02:10 UTCEPSS rescore
  20. 2026-08-15 01:26 UTCEPSS rescore
  21. 2026-08-14 21:24 UTCOSV refresh
  22. 2026-08-13 21:56 UTCEPSS rescore
  23. 2026-08-09 13:42 UTCEPSS rescore
  24. 2026-08-08 16:32 UTCEPSS rescore
  25. 2026-08-07 16:22 UTCEPSS rescore
Show 75 more
  1. 2026-08-06 13:42 UTCEPSS rescore
  2. 2026-08-05 19:12 UTCEPSS rescore
  3. 2026-08-04 15:05 UTCEPSS rescore
  4. 2026-08-04 10:32 UTCEPSS rescore
  5. 2026-08-03 10:30 UTCEPSS rescore
  6. 2026-08-02 02:23 UTCEPSS rescore
  7. 2026-08-01 04:11 UTCEPSS rescore
  8. 2026-07-30 16:24 UTCEPSS rescore
  9. 2026-07-30 10:14 UTCOSV refresh
  10. 2026-07-30 01:26 UTCEPSS rescore
  11. 2026-07-28 15:32 UTCEPSS rescore
  12. 2026-07-26 14:51 UTCEPSS rescore
  13. 2026-07-25 14:13 UTCEPSS rescore
  14. 2026-07-23 14:15 UTCEPSS rescore
  15. 2026-07-23 01:26 UTCEG score recompute
  16. 2026-07-22 22:05 UTCEG score recompute
  17. 2026-07-22 14:04 UTCEPSS rescore
  18. 2026-07-21 15:21 UTCEPSS rescore
  19. 2026-07-21 15:21 UTCEPSS rescore
  20. 2026-07-20 17:04 UTCEPSS rescore
  21. 2026-07-20 17:04 UTCEPSS rescore
  22. 2026-07-19 14:28 UTCEPSS rescore
  23. 2026-07-19 14:28 UTCEPSS rescore
  24. 2026-07-19 02:26 UTCEPSS rescore
  25. 2026-07-19 02:26 UTCEPSS rescore
  26. 2026-07-18 10:00 UTCEPSS rescore
  27. 2026-07-16 16:59 UTCEPSS rescore
  28. 2026-07-16 16:59 UTCEPSS rescore
  29. 2026-07-15 16:54 UTCEPSS rescore
  30. 2026-07-15 16:54 UTCEPSS rescore
  31. 2026-07-15 01:56 UTCEPSS rescore
  32. 2026-07-13 22:26 UTCEPSS rescore
  33. 2026-07-13 06:09 UTCEPSS rescore
  34. 2026-07-12 19:07 UTCOSV refresh
  35. 2026-07-12 05:43 UTCEPSS rescore
  36. 2026-07-11 08:24 UTCEPSS rescore
  37. 2026-07-09 19:06 UTCEPSS rescore
  38. 2026-07-08 15:10 UTCEPSS rescore
  39. 2026-07-07 13:42 UTCEPSS rescore
  40. 2026-07-06 16:24 UTCEPSS rescore
  41. 2026-07-06 02:20 UTCEPSS rescore
  42. 2026-07-05 02:27 UTCEPSS rescore
  43. 2026-07-04 06:28 UTCEPSS rescore
  44. 2026-07-01 15:02 UTCEPSS rescore
  45. 2026-07-01 15:02 UTCEPSS rescore
  46. 2026-06-30 23:19 UTCEPSS rescore
  47. 2026-06-30 23:19 UTCEPSS rescore
  48. 2026-06-29 14:03 UTCEPSS rescore
  49. 2026-06-28 04:53 UTCEPSS rescore
  50. 2026-06-27 03:05 UTCEPSS rescore
  51. 2026-06-25 13:47 UTCEPSS rescore
  52. 2026-06-25 13:47 UTCEPSS rescore
  53. 2026-06-24 14:02 UTCEPSS rescore
  54. 2026-06-24 03:29 UTCOSV refresh
  55. 2026-06-23 21:30 UTCEPSS rescore
  56. 2026-06-22 14:23 UTCEPSS rescore
  57. 2026-06-22 14:23 UTCEPSS rescore
  58. 2026-06-21 14:54 UTCEPSS rescore
  59. 2026-06-21 14:54 UTCEPSS rescore
  60. 2026-06-21 01:57 UTCEPSS rescore
  61. 2026-06-21 01:57 UTCEPSS rescore
  62. 2026-06-19 19:23 UTCEPSS rescore
  63. 2026-06-19 19:23 UTCEPSS rescore
  64. 2026-06-18 17:50 UTCEPSS rescore
  65. 2026-06-17 17:50 UTCEPSS rescore
  66. 2026-06-16 17:50 UTCEPSS rescore
  67. 2026-06-15 17:45 UTCEPSS rescore
  68. 2026-06-13 22:57 UTCEPSS rescore
  69. 2026-06-12 23:09 UTCEPSS rescore
  70. 2026-06-11 13:57 UTCEPSS rescore
  71. 2026-06-10 22:15 UTCEPSS rescore
  72. 2026-06-08 14:14 UTCEPSS rescore
  73. 2026-06-07 15:22 UTCEPSS rescore
  74. 2026-06-07 15:22 UTCEPSS rescore
  75. 2026-06-07 08:50 UTCOSV refresh

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2017-11509?
CVE-2017-11509 is a high vulnerability published on March 28, 2018. An authenticated remote attacker can execute arbitrary code in Firebird SQL Server versions 2.5.7 and 3.0.2 by executing a malformed SQL statement.
When was CVE-2017-11509 disclosed?
CVE-2017-11509 was first published in the National Vulnerability Database on March 28, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-11509 actively exploited?
CVE-2017-11509 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6% probability of exploitation in the next 30 days, which ranks it in the top 7.0% of all scored CVEs.
What is the CVSS score of CVE-2017-11509?
CVE-2017-11509 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2017-11509?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-11509, 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-2017-11509

Explore →

Is Your Infrastructure Affected by CVE-2017-11509?

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

Start Free Scan →Browse All CVEs