# CVE-2015-6851: Security feature bypass in n/a

> Physically proximate attackers can bypass privacy-screen protection on unattended workstations using DOM Inspector in RSA SecurID Web Agent.

- **Severity:** Medium 6.7 (`CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Dec 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-4hrg-5rwg-fx9h

## What is CVE-2015-6851?

CVE-2015-6851 is a medium-severity vulnerability in n/a, published on 23 Dec 2015. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

EMC RSA SecurID Web Agent before 8.0 allows physically proximate attackers to bypass the privacy-screen protection mechanism by leveraging an unattended workstation and running DOM Inspector.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2015-6851?

It affects 1 product.


Products: Rsa Securid Web Agent.

## How do I fix CVE-2015-6851?

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

## Is CVE-2015-6851 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-1471](https://insights.sbomify.com/CVE-2005-1471/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-6851 and fix it if it is affected.

What it is: CVE-2015-6851 is a medium-severity vulnerability in n/a, published on 23 Dec 2015. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-6851 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-2015-6851/ (Markdown: https://insights.sbomify.com/CVE-2015-6851/index.md)
```

## Sources

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

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