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

> Remote attackers can execute arbitrary code via stack-based buffer overflows in Borland InterBase database server functions.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-cm4p-rvrm-3xfj

## What is CVE-2007-5243?

CVE-2007-5243 is a critical memory corruption vulnerability in n/a, published on 6 Oct 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple stack-based buffer overflows in Borland InterBase LI 8.0.0.53 through 8.1.0.253, and WI 5.1.1.680 through 8.1.0.257, allow remote attackers to execute arbitrary code via (1) a long service attach request on TCP port 3050 to the (a) SVC_attach or (b) INET_connect function, (2) a long create request on TCP port 3050 to the (c) isc_create_database or (d) jrd8_create_database function, (3) a long attach request on TCP port 3050 to the (e) isc_attach_database or (f) PWD_db_aliased function, or unspecified vectors involving the (4) jrd8_attach_database or (5) expand_filename2 function.

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

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

It affects 1 product.


Products: Borland Software Interbase.

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

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

## Is CVE-2007-5243 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-5243 exists.

Public exploit code:

- Borland Interbase 2007/2007 SP2 - 'jrd8_create_database' Remote Buffer Overflow (Metasploit) (exploitdb)
- Borland Interbase 2007/2007 SP2 - 'INET_connect' Remote Buffer Overflow (Metasploit) (exploitdb)
- Borland Interbase 2007 - 'PWD_db_aliased' Remote Buffer Overflow (Metasploit) (exploitdb)
- Borland InterBase INET_connect() Buffer Overflow (metasploit)
- Borland InterBase jrd8_create_database() Buffer Overflow (metasploit)
- Borland InterBase PWD_db_aliased() Buffer Overflow (metasploit)

## Other vulnerabilities in n/a

- [CVE-2001-0008](https://insights.sbomify.com/CVE-2001-0008/): Auth bypass in n/a (critical 10.0)
- [CVE-2007-5244](https://insights.sbomify.com/CVE-2007-5244/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-3566](https://insights.sbomify.com/CVE-2007-3566/): Memory corruption in n/a (high 7.5)
- [CVE-2004-1833](https://insights.sbomify.com/CVE-2004-1833/): Misconfiguration in n/a (high 7.5)
- [CVE-2002-1514](https://insights.sbomify.com/CVE-2002-1514/): Path traversal in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-5243 is a critical memory corruption vulnerability in n/a, published on 6 Oct 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-5243 exists.

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-5243/ (Markdown: https://insights.sbomify.com/CVE-2007-5243/index.md)
```

## Sources

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

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