# CVE-2004-0197: Memory corruption in n/a

> Remote attackers can execute arbitrary code via a specially crafted database query exploiting a buffer overflow in the Microsoft Jet Database Engine.

- **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:** 16 Apr 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-gpjv-p254-pq8q

## What is CVE-2004-0197?

CVE-2004-0197 is a high-severity memory corruption vulnerability in n/a, published on 16 Apr 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in Microsoft Jet Database Engine 4.0 allows remote attackers to execute arbitrary code via a specially-crafted database query.

## Which versions are affected by CVE-2004-0197?

It affects 1 product.


Products: Microsoft Jet.

## How do I fix CVE-2004-0197?

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

## Is CVE-2004-0197 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-6026](https://insights.sbomify.com/CVE-2007-6026/): Memory corruption in n/a (critical 9.3)
- [CVE-2000-0323](https://insights.sbomify.com/CVE-2000-0323/): Other in n/a (high 7.6)
- [CVE-2005-0944](https://insights.sbomify.com/CVE-2005-0944/): Code injection in n/a (high 7.5)
- [CVE-2002-0859](https://insights.sbomify.com/CVE-2002-0859/): Memory corruption in n/a (high 7.5)
- [CVE-2000-0325](https://insights.sbomify.com/CVE-2000-0325/): Code injection in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-0197 and fix it if it is affected.

What it is: CVE-2004-0197 is a high-severity memory corruption vulnerability in n/a, published on 16 Apr 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2004-0197 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-2004-0197/ (Markdown: https://insights.sbomify.com/CVE-2004-0197/index.md)
```

## Sources

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

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