# CVE-2007-3572: Command injection in n/a

> Remote attackers can execute arbitrary commands on Yoggie Pico devices via shell metacharacters in the web interface diagnostics script.

- **Severity:** Critical 9.3 (`AV:N/AC:M/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:** 5 Jul 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-43pp-4gq9-93xw

## What is CVE-2007-3572?

CVE-2007-3572 is a critical command injection vulnerability in n/a, published on 5 Jul 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Incomplete blacklist vulnerability in cgi-bin/runDiagnostics.cgi in the web interface on the Yoggie Pico and Pico Pro allows remote attackers to execute arbitrary commands via shell metacharacters in the param parameter, as demonstrated by URL encoded "`" (backtick) characters (%60 sequences).

## Which versions are affected by CVE-2007-3572?

It affects 2 products.


Products: Yoggie Pico, Yoggie Pico Pro.

## How do I fix CVE-2007-3572?

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

## Is CVE-2007-3572 being exploited?

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

Public exploit code:

- Yoggie Pico and Pico Pro Backticks - Remote Code Execution (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-3572 and fix it if it is affected.

What it is: CVE-2007-3572 is a critical command injection vulnerability in n/a, published on 5 Jul 2007. 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-2007-3572 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-2007-3572/ (Markdown: https://insights.sbomify.com/CVE-2007-3572/index.md)
```

## Sources

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

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