# CVE-1999-0147: Command injection in n/a

> Remote attackers can execute arbitrary commands via the aglimpse CGI program in the Glimpse package.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Sep 1999
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-j92f-fc3c-68gj

## What is CVE-1999-0147?

CVE-1999-0147 is a high-severity command injection vulnerability in n/a, published on 29 Sep 1999. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The aglimpse CGI program of the Glimpse package allows remote execution of arbitrary commands.

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

It affects 2 products.


Products: University of Arizona Glimpse Http, University of Arizona Webglimpse.

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

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

## Is CVE-1999-0147 being exploited?

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

Public exploit code:

- GlimpseHTTP 1.0/2.0 / WebGlimpse 1.0 - Piped Command (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-1999-0147 is a high-severity command injection vulnerability in n/a, published on 29 Sep 1999. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-1999-0147 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-1999-0147/ (Markdown: https://insights.sbomify.com/CVE-1999-0147/index.md)
```

## Sources

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

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