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

> Local attackers with physical access can bypass desktop protection controls by killing processes or booting from external media.

- **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:** 12 Sep 2001
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-ffq3-gg7h-pv97

## What is CVE-1999-1443?

CVE-1999-1443 is a medium-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

Micah Software Full Armor Network Configurator and Zero Administration allow local users with physical access to bypass the desktop protection by (1) using <CTRL><ALT><DEL> and kill the process using the task manager, (2) booting the system from a separate disk, or (3) interrupting certain processes that execute while the system is booting.

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

It affects 1 product.


Products: Micah Software Full Armor.

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

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

## Is CVE-1999-1443 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-1999-1443 is a medium-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-1443 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-1443/ (Markdown: https://insights.sbomify.com/CVE-1999-1443/index.md)
```

## Sources

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

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