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

> Remote authenticated users can obtain sensitive information by reading error messages in EMC RSA Data Loss Prevention.

- **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:** 3 May 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-hgg9-9p97-8q6j

## What is CVE-2016-0893?

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

### Official description

EMC RSA Data Loss Prevention 9.6 before SP2 P5 allows remote authenticated users to obtain sensitive information by reading error messages.

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

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

It affects 1 product.


Products: Emc Rsa Data Loss Prevention.

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

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

## Is CVE-2016-0893 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-0894](https://insights.sbomify.com/CVE-2016-0894/): Missing authorization in n/a (medium 6.3)
- [CVE-2016-0892](https://insights.sbomify.com/CVE-2016-0892/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2016-0895](https://insights.sbomify.com/CVE-2016-0895/): Other in n/a (medium 4.3)
- [CVE-2014-0624](https://insights.sbomify.com/CVE-2014-0624/): Privilege escalation in n/a (low 2.7)

## Fix prompt for AI coding agents

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

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

## Sources

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

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