CVE-2002-1940: LCC-Win32 3.2 compiler, when running on Windows 95, 98, or ME, writes portions of previously used memory after

Routine

MEDIUM 5.0DOWNGRADE

CVE-2002-1940 is a medium-severity flaw (CVSS 5.0) affecting lcc-win32. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

No elevated risk signals yet

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	5.0 (Medium)
EPSS exploit chance	1.1% (top 33%)
CISA exploited list	No
Published	2002-12-31
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: jacob navia

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2002-12-31 05:00 UTCPublished CVE record published
2026-06-16 22:00 UTCUpdated Record last modified

jacob navia lcc-win32 DOWNGRADE

Affected: 3.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 3.2

1. Check installed version

apt-cache policy lcc-win32 || rpm -q lcc-win32 || lcc-win32 --version

2. No fixed release: DOWNGRADE to a release before 3.2 (Debian / Ubuntu)

apt-cache madison lcc-win32 sudo apt install lcc-win32=<VERSION_BEFORE_3.2> sudo apt-mark hold lcc-win32

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list lcc-win32 sudo dnf downgrade lcc-win32-<VERSION_BEFORE_3.2> sudo dnf versionlock add lcc-win32

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2002-1940?

lcc-win32: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2002-1940 being exploited?

CVE-2002-1940 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2002-1940 affect?

CVE-2002-1940 affects lcc-win32. Severity is medium (CVSS 5.0). 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

How urgent is CVE-2002-1940?

Priority 34/100. No elevated risk signals yet.

Software pages

Windows vulnerabilities

References

← Back to latest CVEs