# CVE-2014-2650: Command injection in n/a

> Attackers can execute arbitrary OS commands via the web management interface of Unify OpenStage and OpenScape Desk Phone IP devices.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jan 2020
- **Updated:** 6 Aug 2024
- **Also known as:** CVE-2014-2984, GHSA-2rm4-vgjw-r4jw

## What is CVE-2014-2650?

CVE-2014-2650 is a critical command injection vulnerability in n/a, published on 9 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unify OpenStage / OpenScape Desk Phone IP before V3 R3.11.0 SIP has an OS command injection vulnerability in the web based management interface

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 15 products.


Products: Atos Openscape Desk Phone Ip 35g Eco Firmware, Atos Openscape Desk Phone Ip 35g Firmware, Atos Openscape Desk Phone Ip 55g Firmware, Atos Openstage 15 Firmware, Atos Openstage 15 G Firmware, Atos Openstage 20 E Firmware, Atos Openstage 20 Firmware, Atos Openstage 20 G Firmware, Atos Openstage 40 Firmware, Atos Openstage 40 G Firmware, Atos Openstage 5 Firmware, Atos Openstage 60 Firmware, Atos Openstage 60 G Firmware, Atos Openstage 80 Firmware, Atos Openstage 80 G Firmware.

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

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

## Is CVE-2014-2650 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-2651](https://insights.sbomify.com/CVE-2014-2651/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-2650 is a critical command injection vulnerability in n/a, published on 9 Jan 2020. 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-2650 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-2650/ (Markdown: https://insights.sbomify.com/CVE-2014-2650/index.md)
```

## Sources

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

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