# CVE-2011-2763: Command injection in n/a

> Remote attackers can execute arbitrary commands on LifeSize Room appliances via a modified request to the web interface.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Sep 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-w5h8-693r-qmf6

## What is CVE-2011-2763?

CVE-2011-2763 is a high-severity command injection vulnerability in n/a, published on 2 Sep 2011. It can be exploited over the network, with no action from the victim.

### Official description

The web interface on the LifeSize Room appliance LS_RM1_3.5.3 (11) and 4.7.18 allows remote attackers to execute arbitrary commands via a modified request to the LSRoom_Remoting.doCommand function in gateway.php.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2011-2763?

It affects 1 product.


Products: Lifesize Lifesize Room Appliance Software.

## How do I fix CVE-2011-2763?

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

## Is CVE-2011-2763 being exploited?

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

Public exploit code:

- LifeSize Room Command Injection (metasploit)
- LifeSize Room - Command Injection (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2011-2762](https://insights.sbomify.com/CVE-2011-2762/): Auth bypass in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-2763 and fix it if it is affected.

What it is: CVE-2011-2763 is a high-severity command injection vulnerability in n/a, published on 2 Sep 2011. It can be exploited over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-2763 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-2011-2763/ (Markdown: https://insights.sbomify.com/CVE-2011-2763/index.md)
```

## Sources

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

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