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

> Remote authenticated users can obtain sensitive User Detail Popup information via a modified URL in RSA Identity Management.

- **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:** 24 Sep 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rj7j-4622-7jvj

## What is CVE-2016-0918?

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

### Official description

EMC RSA Identity Management and Governance before 6.8.1 P25 and 6.9.x before 6.9.1 P15 and RSA Via Lifecycle and Governance before 7.0.0 P04 allow remote authenticated users to obtain User Detail Popup information via a modified URL.

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

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

It affects 2 products.


Products: Emc Rsa Identity Management and Governance, Emc Rsa via Lifecycle and Governance.

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

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

## Is CVE-2016-0918 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-4619](https://insights.sbomify.com/CVE-2014-4619/): Auth bypass in n/a (critical 9.3)
- [CVE-2015-0532](https://insights.sbomify.com/CVE-2015-0532/): Auth bypass in n/a (high 7.5)
- [CVE-2015-4539](https://insights.sbomify.com/CVE-2015-4539/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2015-4540](https://insights.sbomify.com/CVE-2015-4540/): Cross-site scripting in n/a (low 3.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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