# CVE-2005-3330: Command injection in n/a

> Remote attackers can execute arbitrary commands via shell metacharacters in HTTPS URLs processed by the Snoopy library.

- **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:** 27 Oct 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-hf3f-2785-5v5g

## What is CVE-2005-3330?

CVE-2005-3330 is a high-severity command injection vulnerability in n/a, published on 27 Oct 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The _httpsrequest function in Snoopy 1.2, as used in products such as (1) MagpieRSS, (2) WordPress, (3) Ampache, and (4) Jinzora, allows remote attackers to execute arbitrary commands via shell metacharacters in an HTTPS URL to an SSL protected web page, which is not properly handled by the fetch function.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2005-3330?

It affects 1 product.


Products: Snoopy Snoopy.

## How do I fix CVE-2005-3330?

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

## Is CVE-2005-3330 being exploited?

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

Public exploit code:

- Snoopy 0.9x/1.0/1.2 - Arbitrary Command Execution (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-3330 and fix it if it is affected.

What it is: CVE-2005-3330 is a high-severity command injection vulnerability in n/a, published on 27 Oct 2005. 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-2005-3330 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-2005-3330/ (Markdown: https://insights.sbomify.com/CVE-2005-3330/index.md)
```

## Sources

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

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