Debian LinuxOperating system · Debian

CVE-2015-2788

HIGH · 10.0 CVSS v2.0 Published 2015-04-14
Fix available
A fix is available. Upgrade to after 1.18 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Multiple stack-based buffer overflows in the ib_fill_isqlda function in dbdimp.c in DBD-Firebird before 1.19 allow remote attackers to have unspecified impact via unknown vectors that trigger an error condition, related to binding octets to columns.

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

Stack-based buffer overflows in the ib_fill_isqlda function in dbdimp.c in DBD-Firebird (Perl database driver for Firebird) before version 1.19 allow remote attackers to execute arbitrary code via malformed data binding operations that trigger an error condition when binding octets to columns.

MitigationUpgrade DBD-Firebird to version 1.19 or later to obtain the patched version of the ib_fill_isqlda function.

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
Debian LinuxOperating system
Affected:= 7.0
Dbd FirebirdApplication
Affected:<= 1.18

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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. Check if DBD::Firebird Perl module is installed
    Run `perl -MDBD::Firebird -e 1` or list installed Perl modules with `cpan -l | grep -i firebird`
    Affected if The DBD::Firebird Perl module is present on the system
  2. Determine installed DBD-Firebird version
    Execute `perl -MDBD::Firebird -e 'print $DBD::Firebird::VERSION'` to print the version number
    Affected if The version is 1.18 or earlier, or the version cannot be retrieved (indicating an old installation)
  3. Locate the dbdimp.c file containing the vulnerable function
    Find the DBD::Firebird installation path with `perl -e 'print $_ for @INC'` and search for dbdimp.c in those directories
    Affected if The file dbdimp.c exists in the installation and contains the ib_fill_isqlda function
  4. Identify applications using DBD::Firebird data binding
    Search Perl scripts for 'use DBD::Firebird' or 'DBD::Firebird' imports, and check if they perform bind operations using placeholder parameters
    Affected if Applications use DBD::Firebird to bind octet or binary data to columns, which triggers the overflow condition

A system is affected if DBD::Firebird version 1.18 or earlier is installed and applications perform bind operations with octet-type data to Firebird database columns.

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 a release after 1.18
Interim mitigation

Upgrade DBD-Firebird to version 1.19 or later to obtain the patched version of the ib_fill_isqlda function.

Recommended fix Moderate confidence

DBD-Firebird 1.19

  1. Upgrade DBD-Firebird Perl module to version 1.19 or later via CPAN: cpan -i DBD::Firebird or cpanm DBD::Firebird
  2. If using system packages, apply Debian security update for DBD-Firebird in Debian 7.0 (wheezy) or upgrade to a newer Debian release that includes the fixed package
  3. Verify the installed version matches or exceeds 1.19: perl -MDBD::Firebird -e 'print $DBD::Firebird::VERSION'

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

Fix this in Debian Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-2788 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-2015-2788 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