# CVE-2001-0152: Information disclosure in n/a

> Local attackers can recover passwords from Compressed Folders files in Windows 98/Me Plus!, allowing unauthorized access to protected archives.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 May 2001
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-crr7-h677-x96c

## What is CVE-2001-0152?

CVE-2001-0152 is a low-severity vulnerability in n/a, published on 7 May 2001. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The password protection option for the Compressed Folders feature in Plus! for Windows 98 and Windows Me writes password information to a file, which allows local users to recover the passwords and read the compressed folders.

## Which versions are affected by CVE-2001-0152?

It affects 1 product.


Products: Microsoft Plus.

## How do I fix CVE-2001-0152?

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

## Is CVE-2001-0152 being exploited?

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

Public exploit code:

- Windows Gather DynaZIP Saved Password Extraction (metasploit)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-0152 and fix it if it is affected.

What it is: CVE-2001-0152 is a low-severity vulnerability in n/a, published on 7 May 2001. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2001-0152 exists.

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

## Sources

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

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