# CVE-2002-0645: SQL injection in n/a

> Authenticated users can execute arbitrary commands via SQL injection in Microsoft SQL Server 2000 stored procedures.

- **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:** 26 Jul 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-jw23-q9m9-w62p

## What is CVE-2002-0645?

CVE-2002-0645 is a high-severity SQL injection vulnerability in Microsoft Sql Server, published on 26 Jul 2002. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SQL injection vulnerability in stored procedures for Microsoft SQL Server 2000 and Microsoft Desktop Engine (MSDE) 2000 may allow authenticated users to execute arbitrary commands.

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

It affects 2 products.


Products: Microsoft Data Engine, Microsoft Sql Server.

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

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

## Is CVE-2002-0645 being exploited?

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

## Other vulnerabilities in Microsoft Sql Server

- [CVE-2002-1145](https://insights.sbomify.com/CVE-2002-1145/): Privilege escalation in n/a (critical 10.0)
- [CVE-2002-0721](https://insights.sbomify.com/CVE-2002-0721/): Privilege escalation in n/a (critical 10.0)
- [CVE-2008-0086](https://insights.sbomify.com/CVE-2008-0086/): Memory corruption in n/a (critical 9.0)
- [CVE-2008-0106](https://insights.sbomify.com/CVE-2008-0106/): Memory corruption in n/a (critical 9.0)
- [CVE-2008-0107](https://insights.sbomify.com/CVE-2008-0107/): Integer overflow in n/a (critical 9.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-0645 is a high-severity SQL injection vulnerability in Microsoft Sql Server, published on 26 Jul 2002. 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-0645 in the wild and no public exploit code.

Affected product: Microsoft Sql Server. 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-0645/ (Markdown: https://insights.sbomify.com/CVE-2002-0645/index.md)
```

## Sources

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

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