# CVE-2011-0354: Hardcoded credentials in n/a

> Remote attackers can gain root access to Cisco Tandberg video endpoints due to a blank default password in the root account.

- **Severity:** Critical 10.0 (`AV:N/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:** 3 Feb 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-xh4x-ff3x-6rcx

## What is CVE-2011-0354?

CVE-2011-0354 is a critical vulnerability in n/a, published on 3 Feb 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The default configuration of Cisco Tandberg C Series Endpoints, and Tandberg E and EX Personal Video units, with software before TC4.0.0 has a blank password for the root account, which makes it easier for remote attackers to obtain access via an unspecified login method.

Weakness: CWE-255

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

It affects 3 products.


Products: Cisco Tandberg Endpoint, Cisco Tandberg Personal Video Unit, Cisco Tandberg Personal Video Unit Software.

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

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

## Is CVE-2011-0354 being exploited?

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

Public exploit code:

- Tandberg E & EX & C Series Endpoints - Default Root Account Credentials (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-0354 is a critical vulnerability in n/a, published on 3 Feb 2011. 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-2011-0354 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-0354/ (Markdown: https://insights.sbomify.com/CVE-2011-0354/index.md)
```

## Sources

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

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