# CVE-1999-1400: Security feature bypass in n/a

> Local attackers can bypass the password-protected Economist screen saver to access files by launching Internet Explorer while the screen is locked.

- **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:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Sep 2001
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-7cw7-fpf7-gx4h

## What is CVE-1999-1400?

CVE-1999-1400 is a low-severity vulnerability in n/a, published on 12 Sep 2001. 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

The Economist screen saver 1999 with the "Password Protected" option enabled allows users with physical access to the machine to bypass the screen saver and read files by running Internet Explorer while the screen is still locked.

## Which versions are affected by CVE-1999-1400?

It affects 1 product.


Products: The Economist the Economist 1999 Screen Saver.

## How do I fix CVE-1999-1400?

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

## Is CVE-1999-1400 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-1999-1400 and fix it if it is affected.

What it is: CVE-1999-1400 is a low-severity vulnerability in n/a, published on 12 Sep 2001. 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-1999-1400 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-1999-1400/ (Markdown: https://insights.sbomify.com/CVE-1999-1400/index.md)
```

## Sources

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

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