# CVE-2016-6220: Information disclosure in n/a

> An attacker can access sensitive information via the Dashboard and Error Pages in Trend Micro Control Manager.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 7 Aug 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-54jh-f498-frrg

## What is CVE-2016-6220?

CVE-2016-6220 is a high-severity vulnerability in n/a, published on 7 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Information Disclosure vulnerability in the Dashboard and Error Pages in Trend Micro Control Manager SP3 6.0.

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

## Which versions are affected by CVE-2016-6220?

It affects 1 product.


Products: Trendmicro Control Manager.

## How do I fix CVE-2016-6220?

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

## Is CVE-2016-6220 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-10511](https://insights.sbomify.com/CVE-2018-10511/): Server-side request forgery in Trend Micro Control Manager (critical 10.0)
- [CVE-2018-10510](https://insights.sbomify.com/CVE-2018-10510/): Path traversal in Trend Micro Control Manager (critical 9.8)
- [CVE-2018-3601](https://insights.sbomify.com/CVE-2018-3601/): Auth bypass in Trend Micro Control Manager (critical 9.8)
- [CVE-2017-11383](https://insights.sbomify.com/CVE-2017-11383/): SQL injection in n/a (critical 9.8)
- [CVE-2017-11384](https://insights.sbomify.com/CVE-2017-11384/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-6220 and fix it if it is affected.

What it is: CVE-2016-6220 is a high-severity vulnerability in n/a, published on 7 Aug 2017. 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-2016-6220 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-2016-6220/ (Markdown: https://insights.sbomify.com/CVE-2016-6220/index.md)
```

## Sources

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

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