# CVE-2013-7030: Information disclosure in n/a

> Remote attackers can obtain sensitive phone configuration data via TFTP RRQ operations, exposing cleartext credentials in default configurations.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Dec 2013
- **Updated:** 29 Oct 2024
- **Also known as:** GHSA-hxwc-4mmq-5hhj

## What is CVE-2013-7030?

CVE-2013-7030 is a high-severity vulnerability in Cisco Unified Communications Manager, published on 12 Dec 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The TFTP service in Cisco Unified Communications Manager (aka CUCM or Unified CM) allows remote attackers to obtain sensitive information from a phone via an RRQ operation, as demonstrated by discovering a cleartext UseUserCredential field in an SPDefault.cnf.xml file.  NOTE: the vendor reportedly disputes the significance of this report, stating that this is an expected default behavior, and that the product's documentation describes use of the TFTP Encrypted Config option in addressing this issue

Weakness: CWE-310

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

It affects 1 product.


Products: Cisco Unified Communications Manager.

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

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

## Is CVE-2013-7030 being exploited?

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

Public exploit code:

- Cisco Unified Communications Manager - TFTP Service (exploitdb)

## Other vulnerabilities in Cisco Unified Communications Manager

- [CVE-2026-20230](https://insights.sbomify.com/CVE-2026-20230/): Cisco Unified Communications Manager Server-Side Request Forgery (SSRF) (high 8.6, exploited in the wild)
- [CVE-2026-20045](https://insights.sbomify.com/CVE-2026-20045/): Cisco Unified Communications Products Code Injection (high 8.2, exploited in the wild)
- [CVE-2025-20309](https://insights.sbomify.com/CVE-2025-20309/): Cisco Unified Communications Manager Static SSH Credentials Vulnerability (critical 10.0)
- [CVE-2011-1643](https://insights.sbomify.com/CVE-2011-1643/): Information disclosure in n/a (critical 10.0)
- [CVE-2024-20253](https://insights.sbomify.com/CVE-2024-20253/): Deserialization in Cisco Packaged Contact Center Enterprise (critical 9.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-7030 is a high-severity vulnerability in Cisco Unified Communications Manager, published on 12 Dec 2013. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-7030 exists.

Affected product: Cisco Unified Communications Manager. 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-7030/ (Markdown: https://insights.sbomify.com/CVE-2013-7030/index.md)
```

## Sources

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

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