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

> Remote attackers can discover usernames and cleartext passwords by reading error messages from the authentication setup page.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 May 2011
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8wvc-qm7p-5pq5

## What is CVE-2010-0216?

CVE-2010-0216 is a medium-severity vulnerability in n/a, published on 10 May 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

authenticate_ad_setup_finished.cfm in MediaCAST 8 and earlier allows remote attackers to discover usernames and cleartext passwords by reading the error messages returned for requests that use the UserID parameter.

Weakness: CWE-310

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

It affects 1 product.


Products: Inventivetec Mediacast.

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

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

## Is CVE-2010-0216 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-2077](https://insights.sbomify.com/CVE-2011-2077/): Misconfiguration in n/a (high 7.5)
- [CVE-2011-2079](https://insights.sbomify.com/CVE-2011-2079/): XML external entity in n/a (high 7.5)
- [CVE-2011-2080](https://insights.sbomify.com/CVE-2011-2080/): SQL injection in n/a (high 7.5)
- [CVE-2011-2076](https://insights.sbomify.com/CVE-2011-2076/): Information disclosure in n/a (medium 5.0)
- [CVE-2011-2081](https://insights.sbomify.com/CVE-2011-2081/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2010-0216 is a medium-severity vulnerability in n/a, published on 10 May 2011. 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-2010-0216 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-0216/ (Markdown: https://insights.sbomify.com/CVE-2010-0216/index.md)
```

## Sources

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

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