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

> Remote authenticated users can bypass permission controls to view sensitive information from encrypted documents via the PrintScreen button.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **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:** 20 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-v825-395q-5vff

## What is CVE-2016-2406?

CVE-2016-2406 is a medium-severity vulnerability in n/a, published on 20 Mar 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The permission control module in Huawei Document Security Management (aka DSM) before V100R002C05SPC670 allows remote authenticated users to obtain sensitive information from encrypted documents by leveraging incorrect control of permissions on the PrintScreen button.

Weakness: CWE-275

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

It affects 1 product.


Products: Huawei Document Security Management.

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

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

## Is CVE-2016-2406 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-8303](https://insights.sbomify.com/CVE-2015-8303/): Information disclosure in n/a (medium 4.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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