CVE-2010-0391
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 · uneditedMultiple stack-based buffer overflows in Embarcadero Technologies InterBase SMP 2009 9.0.3.437 allow remote attackers to execute arbitrary code via unknown vectors involving crafted packets. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.
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 · moderate confidenceMultiple stack-based buffer overflow vulnerabilities exist in Embarcadero InterBase SMP 2009 (version 9.0.3.437) that allow remote attackers to execute arbitrary code via crafted packets. The specific attack vectors are not detailed, but the vulnerability is remotely exploitable and rated high severity due to the potential for complete system compromise.
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= 9.0.3.437CVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Identify if InterBase is installedCheck for InterBase installation directories (commonly C:\Program Files\Embarcadero\InterBase or C:\InterBase) or query the Windows registry under HKLM\SOFTWARE\Embarcadero\InterBase for the installation path and version.Affected if InterBase SMP 2009 version 9.0.3.437 is installed on the system.
-
Verify the exact InterBase versionLocate the InterBase executable (ibserver.exe or gds_db.exe) in the installation directory and check its file properties for version information, or query the InterBase version via registry or command line if available.Affected if The installed version is exactly 9.0.3.437.
-
Confirm the InterBase service is running and exposedCheck if the InterBase service (typically named InterBase Server or gds_db) is running using Task Manager or sc query, and identify if the service port (usually 3050/tcp) is listening on network interfaces using netstat -an | findstr 3050.Affected if The service is running and bound to a network-accessible interface (not localhost only), making the vulnerability remotely exploitable.
The environment is affected only if Embarcadero InterBase SMP 2009 version 9.0.3.437 is installed and the InterBase service is running and accessible over the network.
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 dataApply vendor-supplied patches for InterBase SMP 2009; if patches are unavailable for this older version, consider upgrading to a supported InterBase version or implementing network segmentation to restrict access to the InterBase service.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-0391 — 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-2010-0391 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