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

> Physically proximate attackers can bypass security controls via USB to sign data, extract keys, and impersonate the device.

- **Severity:** Medium 6.8 (`CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 18 Aug 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-qr3j-7fmq-f3gx

## What is CVE-2015-1878?

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

### Official description

Thales nShield Connect hardware models 500, 1500, 6000, 500+, 1500+, and 6000+ before 11.72 allows physically proximate attackers to sign arbitrary data with previously loaded signing keys, extract the device identification key [KNETI] and impersonate the nShield Connect device on a network, affect the integrity and confidentiality of newly created keys, and potentially cause other unspecified impacts using previously loaded keys by connecting to the USB port on the front panel.

Weakness: CWE-264

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

It affects 1 product.


Products: Thalesesecurity Nshield Connect Firmware.

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

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

## Is CVE-2015-1878 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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