# CVE-2007-2606: Memory corruption in n/a

> Buffer overflows in Firebird database allow attackers to trigger memory corruption, potentially leading to code execution or denial of service.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 11 May 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-v52h-q97r-4w5h

## What is CVE-2007-2606?

CVE-2007-2606 is a high-severity memory corruption vulnerability in n/a, published on 11 May 2007. 

### Official description

Multiple buffer overflows in Firebird 2.1 allow attackers to trigger memory corruption and possibly have other unspecified impact via certain input processed by (1) config\ConfigFile.cpp or (2) msgs\check_msgs.epp.  NOTE: if ConfigFile.cpp reads a configuration file with restrictive permissions, then the ConfigFile.cpp vector may not cross privilege boundaries and perhaps should not be included in CVE.

## Which versions are affected by CVE-2007-2606?

It affects 1 product.


Products: Firebirdsql Firebird.

## How do I fix CVE-2007-2606?

No fix has been published for CVE-2007-2606 yet. Limit exposure of the affected software until one is available.

## Is CVE-2007-2606 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-40342](https://insights.sbomify.com/CVE-2026-40342/): Firebird: Path Traversal + Arbitrary File Write Leads to Remote Code Execution (critical 10.0)
- [CVE-2008-0467](https://insights.sbomify.com/CVE-2008-0467/): Memory corruption in n/a (critical 10.0)
- [CVE-2007-4992](https://insights.sbomify.com/CVE-2007-4992/): Memory corruption in n/a (critical 10.0)
- [CVE-2007-5245](https://insights.sbomify.com/CVE-2007-5245/): Memory corruption in n/a (critical 10.0)
- [CVE-2007-5246](https://insights.sbomify.com/CVE-2007-5246/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-2606 and fix it if it is affected.

What it is: CVE-2007-2606 is a high-severity memory corruption vulnerability in n/a, published on 11 May 2007. 
Exploitation: There is no known exploitation of CVE-2007-2606 in the wild and no public exploit code.

Affected product: n/a. 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-2007-2606/ (Markdown: https://insights.sbomify.com/CVE-2007-2606/index.md)
```

## Sources

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

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