# CVE-2006-1961: Command injection in n/a

> Local attackers can execute arbitrary Linux shell commands via metacharacters in the CLI show command, leading to full system compromise.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-89fx-5fv2-j67w

## What is CVE-2006-1961?

CVE-2006-1961 is a high-severity command injection vulnerability in n/a, published on 21 Apr 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Cisco CiscoWorks Wireless LAN Solution Engine (WLSE) and WLSE Express before 2.13, Hosting Solution Engine (HSE) and User Registration Tool (URT) before 20060419, and all versions of Ethernet Subscriber Solution Engine (ESSE) and CiscoWorks2000 Service Management Solution (SMS) allow local users to gain Linux shell access via shell metacharacters in arguments to the "show" command in the application's command line interface (CLI), aka bug ID CSCsd21502 (WLSE), CSCsd22861 (URT), and CSCsd22859 (HSE).  NOTE: other issues might be addressed by the Cisco advisory.

## Which versions are affected by CVE-2006-1961?

It affects 5 products.


Products: Cisco Ciscoworks 2000 Service Management Solution, Cisco Ethernet Subscriber Solution Engine, Cisco Hosting Solution Engine, Cisco User Registration Tool, Cisco Wireless Lan Solution Engine.

## How do I fix CVE-2006-1961?

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

## Is CVE-2006-1961 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-1961 and fix it if it is affected.

What it is: CVE-2006-1961 is a high-severity command injection vulnerability in n/a, published on 21 Apr 2006. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-1961 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-2006-1961/ (Markdown: https://insights.sbomify.com/CVE-2006-1961/index.md)
```

## Sources

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

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