# CVE-2014-0661: Code injection in n/a

> Remote attackers can execute arbitrary commands or cause denial of service in Cisco TelePresence systems via crafted XML-RPC messages.

- **Severity:** High 8.3 (`AV:A/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:** 22 Jan 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-7g4g-9h43-3xvc

## What is CVE-2014-0661?

CVE-2014-0661 is a high-severity code injection vulnerability in n/a, published on 22 Jan 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The System Status Collection Daemon (SSCD) in Cisco TelePresence System 500-37, 1000, 1300-65, and 3xxx before 1.10.2(42), and 500-32, 1300-47, TX1310 65, and TX9xxx before 6.0.4(11), allows remote attackers to execute arbitrary commands or cause a denial of service (stack memory corruption) via a crafted XML-RPC message, aka Bug ID CSCui32796.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2014-0661?

It affects 14 products.


Products: Cisco Telepresence System 1000, Cisco Telepresence System 1100, Cisco Telepresence System 1300-65, Cisco Telepresence System 3000, Cisco Telepresence System 3010, Cisco Telepresence System 3200, Cisco Telepresence System 3210, Cisco Telepresence System 500-32, Cisco Telepresence System 500-37, Cisco Telepresence System Software, Cisco Telepresence System Tx1300 47, Cisco Telepresence System Tx1310 65, Cisco Telepresence System Tx9000, Cisco Telepresence System Tx9200.

## How do I fix CVE-2014-0661?

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

## Is CVE-2014-0661 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-0372](https://insights.sbomify.com/CVE-2011-0372/): Command injection in n/a (critical 10.0)
- [CVE-2011-0376](https://insights.sbomify.com/CVE-2011-0376/): Information disclosure in n/a (critical 10.0)
- [CVE-2011-0373](https://insights.sbomify.com/CVE-2011-0373/): Command injection in n/a (critical 9.0)
- [CVE-2011-0374](https://insights.sbomify.com/CVE-2011-0374/): Command injection in n/a (critical 9.0)
- [CVE-2011-0375](https://insights.sbomify.com/CVE-2011-0375/): Command injection in n/a (critical 9.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-0661 and fix it if it is affected.

What it is: CVE-2014-0661 is a high-severity code injection vulnerability in n/a, published on 22 Jan 2014. 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-2014-0661 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-2014-0661/ (Markdown: https://insights.sbomify.com/CVE-2014-0661/index.md)
```

## Sources

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

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