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

> Remote attackers can execute arbitrary code and gain database control via a buffer overflow in the password encryption function.

- **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:** 12 Jul 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-fc6r-g93v-xcwr

## What is CVE-2002-0624?

CVE-2002-0624 is a high-severity memory corruption vulnerability in Microsoft Sql Server, published on 12 Jul 2002. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Buffer overflow in the password encryption function of Microsoft SQL Server 2000, including Microsoft SQL Server Desktop Engine (MSDE) 2000, allows remote attackers to gain control of the database and execute arbitrary code via SQL Server Authentication, aka "Unchecked Buffer in Password Encryption Procedure."

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

It affects 2 products.


Products: Microsoft Msde, Microsoft Sql Server.

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

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

## Is CVE-2002-0624 being exploited?

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

Public exploit code:

- Microsoft SQL Server 2000 - Password Encrypt procedure Buffer Overflow (exploitdb)

## Other vulnerabilities in Microsoft Sql Server

- [CVE-2002-0641](https://insights.sbomify.com/CVE-2002-0641/): Memory corruption in n/a (high 7.5)
- [CVE-2002-0642](https://insights.sbomify.com/CVE-2002-0642/): Privilege escalation in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-0624 is a high-severity memory corruption vulnerability in Microsoft Sql Server, published on 12 Jul 2002. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-0624 exists.

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-0624/ (Markdown: https://insights.sbomify.com/CVE-2002-0624/index.md)
```

## Sources

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

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