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

> Remote attackers can execute arbitrary code via a buffer overflow in the database connection function of XAMPP for Windows.

- **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:** 18 Apr 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-98r7-fvm5-pv89

## What is CVE-2007-2079?

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

### Official description

The ADONewConnection Connect function in adodb.php in XAMPP 1.6.0a and earlier for Windows uses untrusted input for the database server hostname, which allows remote attackers to trigger a library buffer overflow and execute arbitrary code via a long host parameter, or have other unspecified impact.  NOTE: it could be argued that this is an issue in mssql_connect (CVE-2007-1411.1) in PHP, or an issue in the ADOdb Library, and the proper fix should be in one of these products; if so, then this should not be treated as a vulnerability in XAMPP.

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

It affects 1 product.


Products: Xampp Apache Distribution.

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

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

## Is CVE-2007-2079 being exploited?

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

Public exploit code:

- XAMPP for Windows 1.6.0a - 'mssql_connect()' Remote Buffer Overflow (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-2080](https://insights.sbomify.com/CVE-2007-2080/): SQL injection in n/a (high 7.5)
- [CVE-2005-1078](https://insights.sbomify.com/CVE-2005-1078/): Hardcoded credentials in n/a (high 7.5)
- [CVE-2005-2043](https://insights.sbomify.com/CVE-2005-2043/): Path traversal in n/a (medium 5.0)
- [CVE-2005-1077](https://insights.sbomify.com/CVE-2005-1077/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-2079 is a critical memory corruption vulnerability in n/a, published on 18 Apr 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-2079 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-2079/ (Markdown: https://insights.sbomify.com/CVE-2007-2079/index.md)
```

## Sources

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

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