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

> Remote attackers can execute arbitrary code via stack-based buffer overflows in the SAP DB Web Server.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jul 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9jvm-5xgq-52vp

## What is CVE-2007-3614?

CVE-2007-3614 is a high-severity memory corruption vulnerability in n/a, published on 6 Jul 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 waHTTP.exe (aka the SAP DB Web Server) in SAP DB, possibly 7.3 through 7.5, allow remote attackers to execute arbitrary code via (1) a certain cookie value; (2) a certain additional parameter, related to sapdbwa_GetQueryString; and other unspecified vectors related to "numerous other fields."

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

It affects 1 product.


Products: Sap Sap Db.

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

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

## Is CVE-2007-3614 being exploited?

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

Public exploit code:

- SAP DB 7.x Web Server - 'WAHTTP.exe' Multiple Buffer Overflow Vulnerabilities (exploitdb)
- SAP DB 7.4 WebTools Buffer Overflow (metasploit)
- SAP DB 7.4 - WebTools Remote Overwrite (SEH) (exploitdb)
- SAP DB 7.4 - WebTools Buffer Overflow (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2003-0939](https://insights.sbomify.com/CVE-2003-0939/): Memory corruption in n/a (high 7.5)
- [CVE-2003-0941](https://insights.sbomify.com/CVE-2003-0941/): Missing authorization in n/a (high 7.5)
- [CVE-2003-0942](https://insights.sbomify.com/CVE-2003-0942/): Memory corruption in n/a (high 7.5)
- [CVE-2003-0943](https://insights.sbomify.com/CVE-2003-0943/): Information disclosure in n/a (high 7.5)
- [CVE-2003-0944](https://insights.sbomify.com/CVE-2003-0944/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-3614 is a high-severity memory corruption vulnerability in n/a, published on 6 Jul 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-3614 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-3614/ (Markdown: https://insights.sbomify.com/CVE-2007-3614/index.md)
```

## Sources

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

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