# CVE-2000-0271: Information disclosure in n/a

> An attacker with local access can read unencrypted passwords from Emacs history due to improper clearing of typed keys.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/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:** 26 Apr 2000
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-7mr4-hhph-pp56

## What is CVE-2000-0271?

CVE-2000-0271 is a medium-severity vulnerability in n/a, published on 26 Apr 2000. 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

read-passwd and other Lisp functions in Emacs 20 do not properly clear the history of recently typed keys, which allows an attacker to read unencrypted passwords.

## Which versions are affected by CVE-2000-0271?

It affects 1 product.


Products: Gnu Emacs.

## How do I fix CVE-2000-0271?

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

## Is CVE-2000-0271 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-6109](https://insights.sbomify.com/CVE-2007-6109/): Memory corruption in n/a (critical 10.0)
- [CVE-2024-39331](https://insights.sbomify.com/CVE-2024-39331/): Code injection in n/a (critical 9.8)
- [CVE-2024-53920](https://insights.sbomify.com/CVE-2024-53920/): Code injection in n/a (high 7.8)
- [CVE-2024-30202](https://insights.sbomify.com/CVE-2024-30202/): Code injection in n/a (high 7.8)
- [CVE-2023-2491](https://insights.sbomify.com/CVE-2023-2491/): Command injection in emacs (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2000-0271 and fix it if it is affected.

What it is: CVE-2000-0271 is a medium-severity vulnerability in n/a, published on 26 Apr 2000. 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-2000-0271 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-2000-0271/ (Markdown: https://insights.sbomify.com/CVE-2000-0271/index.md)
```

## Sources

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

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