# CVE-2015-2788: Memory corruption in n/a

> Remote attackers can trigger stack-based buffer overflows in the DBD-Firebird Perl driver, potentially leading to code execution or denial of service.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Apr 2015
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-2788, DSA-3219-1, GHSA-g3xf-fc3r-hm24, MGASA-2015-0159, UBUNTU-CVE-2015-2788

## What is CVE-2015-2788?

CVE-2015-2788 is a critical memory corruption vulnerability in Debian Debian Linux, published on 14 Apr 2015. It can be exploited over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2015-2788?

It affects 2 products.


Products: Debian Dbd-Firebird, Debian Debian Linux.

## How do I fix CVE-2015-2788?

Upgrade to a fixed version.

## Is CVE-2015-2788 being exploited?

There is no known exploitation of CVE-2015-2788 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-2788 and fix it if it is affected.

What it is: CVE-2015-2788 is a critical memory corruption vulnerability in Debian Debian Linux, published on 14 Apr 2015. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-2788 in the wild and no public exploit code.

Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2015-2788/ (Markdown: https://insights.sbomify.com/CVE-2015-2788/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2015-2788
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-2788
- OSV: https://osv.dev/vulnerability/CVE-2015-2788

---
From sbomify Insights: https://insights.sbomify.com/CVE-2015-2788/
Summaries are generated and may contain mistakes; the official description above is the record.