# CVE-2010-0572: Information disclosure in n/a

> Authenticated users can discover Cisco Digital Media Player credentials by reading error logs or stack traces in Cisco Digital Media Manager.

- **Severity:** High 7.1 (`AV:N/AC:H/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Mar 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-j4f4-j4v7-f684

## What is CVE-2010-0572?

CVE-2010-0572 is a high-severity vulnerability in n/a, published on 5 Mar 2010. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Cisco Digital Media Manager (DMM) before 5.2 allows remote authenticated users to discover Cisco Digital Media Player credentials via vectors related to reading a (1) error log or (2) stack trace, aka Bug ID CSCtc46050.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2010-0572?

It affects 1 product.


Products: Cisco Digital Media Manager.

## How do I fix CVE-2010-0572?

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

## Is CVE-2010-0572 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-0570](https://insights.sbomify.com/CVE-2010-0570/): Hardcoded credentials in n/a (critical 10.0)
- [CVE-2012-0329](https://insights.sbomify.com/CVE-2012-0329/): Code injection in n/a (critical 9.0)
- [CVE-2010-0571](https://insights.sbomify.com/CVE-2010-0571/): Privilege escalation in n/a (high 8.5)
- [CVE-2013-3446](https://insights.sbomify.com/CVE-2013-3446/): Open redirect in n/a (medium 5.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-0572 and fix it if it is affected.

What it is: CVE-2010-0572 is a high-severity vulnerability in n/a, published on 5 Mar 2010. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-0572 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-2010-0572/ (Markdown: https://insights.sbomify.com/CVE-2010-0572/index.md)
```

## Sources

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

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