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

> Attackers can execute arbitrary code by placing a file with a long extension in a folder targeted by the Windows 95 backup utility.

- **Severity:** Low 3.6 (`AV:L/AC:L/Au:N/C:N/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Jun 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-6rq9-vhjr-cg53

## What is CVE-2002-1692?

CVE-2002-1692 is a low-severity memory corruption vulnerability in n/a, published on 21 Jun 2005. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Buffer overflow in backup utility of Microsoft Windows 95 allows attackers to execute arbitrary code by causing a filename with a long extension to be placed in a folder to be backed up.

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

It affects 1 product.


Products: Microsoft Windows 95.

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

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

## Is CVE-2002-1692 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-1999-0387](https://insights.sbomify.com/CVE-1999-0387/): Information disclosure in n/a (high 7.8)
- [CVE-2000-0330](https://insights.sbomify.com/CVE-2000-0330/): Memory corruption in n/a (high 7.6)
- [CVE-1999-0518](https://insights.sbomify.com/CVE-1999-0518/): Weak cryptography in n/a (high 7.5)
- [CVE-2000-0155](https://insights.sbomify.com/CVE-2000-0155/): Code injection in n/a (high 7.2)
- [CVE-2000-0979](https://insights.sbomify.com/CVE-2000-0979/): Auth bypass in n/a (medium 6.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-1692 is a low-severity memory corruption vulnerability in n/a, published on 21 Jun 2005. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2002-1692 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-1692/ (Markdown: https://insights.sbomify.com/CVE-2002-1692/index.md)
```

## Sources

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

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