# CVE-2002-1940: Information disclosure in n/a

> Local attackers can read sensitive memory data due to OS-level memory handling flaws in Windows 95/98/ME when using LCC-Win32.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jun 2005
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-h7m9-hhqw-vp2c

## What is CVE-2002-1940?

CVE-2002-1940 is a medium-severity vulnerability in n/a, published on 28 Jun 2005. 

### Official description

LCC-Win32 3.2 compiler, when running on Windows 95, 98, or ME, writes portions of previously used memory after the import table, which could allow attackers to gain sensitive information.  NOTE: it has been reported that this problem is due to the OS and not the application.

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

It affects 1 product.


Products: Jacob Navia Lcc-Win32.

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

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

## Is CVE-2002-1940 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2002-1940 is a medium-severity vulnerability in n/a, published on 28 Jun 2005. 
Exploitation: There is no known exploitation of CVE-2002-1940 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-1940/ (Markdown: https://insights.sbomify.com/CVE-2002-1940/index.md)
```

## Sources

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

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