# CVE-2002-1874: Command injection in n/a

> Remote attackers can execute arbitrary commands on AstroCam systems via shell metacharacters in HTTP requests to astrocam.cgi.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jun 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-hf87-4rwf-j97v

## What is CVE-2002-1874?

CVE-2002-1874 is a critical command injection vulnerability in n/a, published on 28 Jun 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

astrocam.cgi in AstroCam 0.9-1-1 through 1.4.0 allows remote attackers to execute arbitrary commands via shell metacharacters in an HTTP request.  NOTE: earlier disclosures stated that the affected versions were 1.7.1 through 2.1.2, but the vendor explicitly stated that these were incorrect.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2002-1874?

It affects 1 product.


Products: Astrocam Astrocam.

## How do I fix CVE-2002-1874?

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

## Is CVE-2002-1874 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-1426](https://insights.sbomify.com/CVE-2007-1426/): Denial of service in n/a (high 7.8)
- [CVE-2008-2075](https://insights.sbomify.com/CVE-2008-2075/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-1874 and fix it if it is affected.

What it is: CVE-2002-1874 is a critical command injection vulnerability in n/a, published on 28 Jun 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2002-1874 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-2002-1874/ (Markdown: https://insights.sbomify.com/CVE-2002-1874/index.md)
```

## Sources

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

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