# CVE-2013-3454: Hardcoded credentials in n/a

> Remote attackers can exploit a default password for the pwrecovery account to modify configurations or perform arbitrary actions on Cisco TelePresence devices.

- **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:** 8 Aug 2013
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-79wc-qq86-gqcv

## What is CVE-2013-3454?

CVE-2013-3454 is a critical vulnerability in n/a, published on 8 Aug 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cisco TelePresence System Software 1.10.1 and earlier on 500, 13X0, 1X00, 30X0, and 3X00 devices, and 6.0.3 and earlier on TX 9X00 devices, has a default password for the pwrecovery account, which makes it easier for remote attackers to modify the configuration or perform arbitrary actions via HTTPS requests, aka Bug ID CSCui43128.

Weakness: CWE-255

## Which versions are affected by CVE-2013-3454?

It affects 11 products.


Products: Cisco Telepresence System 1300, 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 Tx9000, Cisco Telepresence System Tx9200.

## How do I fix CVE-2013-3454?

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

## Is CVE-2013-3454 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-3454 and fix it if it is affected.

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

## Sources

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

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