dbcve.org
FirebirdApplication · Firebirdsql

CVE-2025-65104

HIGH · 7.5 CVSS v3.1 Published 2026-04-17
Fix available
A fix is available. Upgrade to 3.0.14 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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.

NVD · unedited
Firebird is an open-source relational database management system. In versions FB3 of the client library placed incorrect data length values into XSQLDA fields when communicating with FB4 or higher servers, resulting in an information leak. This issue is fixed by upgrading to the FB4 client or higher.

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.

dbcve analysis · high confidence

The Firebird 3 client library incorrectly populates data length values in XSQLDA (Extended SQL Descriptor Area) fields when communicating with Firebird 4 or higher servers, causing an information leak through disclosure of incorrect metadata about returned data values.

MitigationUpgrade Firebird client libraries from version 3 to version 4 or higher to obtain the corrected XSQLDA length field handling.

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

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.

NVD · CPE data
FirebirdApplication
Affected:< 3.0.14

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.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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.

dbcve checks

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

  1. Identify installed Firebird client library version
    On Linux, run 'dpkg -l | grep firebird' or 'rpm -qa | grep firebird' to list installed Firebird packages. On Windows, check the file version of fbclient.dll in the Firebird bin directory or system32 folder.
    Affected if The Firebird client library package version is shown as less than 3.0.14
  2. Locate the Firebird client library file
    Search for libfbclient.so (Linux) or fbclient.dll (Windows) on the system using 'find / -name libfbclient.so 2>/dev/null' or checking typical installation paths like /usr/lib/firebird or C:\Program Files\Firebird\
    Affected if The library file exists and its embedded version information (viewable via 'strings' or file properties) shows a version below 3.0.14
  3. Determine if client connects to Firebird 4 or higher servers
    Review application configuration, connection strings, or database server addresses to identify if any connections target Firebird server version 4.0 or higher. Check connection parameters or server inventory for the target Firebird server version.
    Affected if The Firebird client library version is below 3.0.14 AND the application connects to any Firebird 4.0 or higher database server

You are affected if the Firebird client library version is below 3.0.14 AND your application connects to Firebird server version 4.0 or higher, causing incorrect XSQLDA length field population during queries.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 3.0.14 or later
Fixed in 3.0.14
Interim mitigation

Upgrade Firebird client libraries from version 3 to version 4 or higher to obtain the corrected XSQLDA length field handling.

Recommended fix Moderate confidence

Firebird 4.x client library

  1. 1. Identify all systems running Firebird FB3 (version 3.x) client libraries that connect to Firebird 4 or higher servers
  2. 2. Download the Firebird 4.x client library from the official Firebird project (firebirdsql.org)
  3. 3. Replace the existing FB3 client library (libfbclient.so or fbclient.dll) on all affected client systems with the FB4 client library
  4. 4. Ensure the new client library is in the system library path or application's library search path
  5. 5. Test database connections from affected clients to the Firebird 4+ servers to verify the information leak is resolved
  6. 6. Verify that applications function correctly with the new client library before deploying to production
Caveat Upgrading from FB3 to FB4 client library may require testing for API/behavioral changes; review Firebird 4 release notes for any client-side compatibility notes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Firebird Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-65104 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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