# CVE-2002-0695: Memory corruption in n/a

> Remote attackers can execute arbitrary code via a buffer overflow in the T-SQL OpenRowSet component of Microsoft Data Access Components.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Apr 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-gj9p-2pjp-8vjq

## What is CVE-2002-0695?

CVE-2002-0695 is a high-severity memory corruption vulnerability in n/a, published on 2 Apr 2003. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Buffer overflow in the Transact-SQL (T-SQL) OpenRowSet component of Microsoft Data Access Components (MDAC) 2.5 through 2.7 for SQL Server 7.0 or 2000 allows remote attackers to execute arbitrary code via a query that calls the OpenRowSet command.

## Which versions are affected by CVE-2002-0695?

It affects 2 products.


Products: Microsoft Data Access Components, Microsoft Microsoft Data Access Components.

## How do I fix CVE-2002-0695?

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

## Is CVE-2002-0695 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-1918](https://insights.sbomify.com/CVE-2002-1918/): Memory corruption in n/a (critical 10.0)
- [CVE-2003-0903](https://insights.sbomify.com/CVE-2003-0903/): Memory corruption in n/a (critical 10.0)
- [CVE-1999-1011](https://insights.sbomify.com/CVE-1999-1011/): Command injection in n/a (critical 10.0)
- [CVE-2012-1891](https://insights.sbomify.com/CVE-2012-1891/): Memory corruption in n/a (critical 9.8)
- [CVE-2011-0026](https://insights.sbomify.com/CVE-2011-0026/): Integer overflow in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-0695 and fix it if it is affected.

What it is: CVE-2002-0695 is a high-severity memory corruption vulnerability in n/a, published on 2 Apr 2003. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2002-0695 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-2002-0695/ (Markdown: https://insights.sbomify.com/CVE-2002-0695/index.md)
```

## Sources

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

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