CVE-2008-0387
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 · uneditedInteger overflow in Firebird SQL 1.0.3 and earlier, 1.5.x before 1.5.6, 2.0.x before 2.0.4, and 2.1.x before 2.1.0 RC1 might allow remote attackers to execute arbitrary code via crafted (1) op_receive, (2) op_start, (3) op_start_and_receive, (4) op_send, (5) op_start_and_send, and (6) op_start_send_and_receive XDR requests, which triggers memory corruption.
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 confidenceInteger overflow in Firebird SQL's XDR request handling allows remote attackers to send crafted op_receive, op_start, op_start_and_receive, op_send, op_start_and_send, and op_start_send_and_receive requests that corrupt memory and potentially execute arbitrary code.
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<= 1.0.3>= 1.5, < 1.5.6>= 2.0.0, < 2.0.4= 2.1.0CVSS 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
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:L/Au:N/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed Firebird SQL versionRun the following command to query the Firebird version: isql -z -u SYSDBA -p masterkey localhost:service_mgr -e 'SELECT rdb$get_context('SYSTEM','ENGINE_VERSION') from rdb$database;' 2>/dev/null || fbstat -version 2>/dev/null || check the version string in the Firebird binary (typically located in /opt/firebird/bin/ or C:\Program Files\Firebird\Firebird_2_x\)Affected if The version falls within <= 1.0.3, >= 1.5.0 and < 1.5.6, >= 2.0.0 and < 2.0.4, or equals 2.1.0 exactly
-
Verify Firebird server is running and listening for connectionsRun 'netstat -an | grep 3050' on Linux/Unix or 'netstat -an | findstr 3050' on Windows to check if port 3050/tcp is in LISTEN state. Alternatively, run 'nmap -p 3050 localhost' if available.Affected if The server is listening on port 3050/tcp, indicating network exposure of the vulnerable XDR handling code
-
Confirm remote network access is enabled in Firebird configurationInspect the firebird.conf configuration file (typically in /etc/firebird/ or the Firebird installation directory). Look for the RemoteBindAddress setting or check if the default 3050 port binding allows external connections. Also verify that the server is bound to a non-loopback interface.Affected if RemoteBindAddress is set to an IP address accessible from untrusted networks, or the server accepts connections on interfaces other than localhost/127.0.0.1
You are affected if your installed Firebird version is within the vulnerable ranges and the server is accessible over the network on port 3050/tcp, enabling remote attackers to send crafted XDR requests.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data1.5.62.0.4
Upgrade Firebird SQL to version 1.5.6+, 2.0.4+, or 2.1.0+ to patch the integer overflow. If immediate patching is not feasible, restrict network access to the Firebird server port (3050/tcp) to trusted clients only.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-0387 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2008-0387 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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