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

> Authenticated users with crypto-user or crypto-officer access can bypass key-export restrictions on Gemalto SafeNet Luna HSMs.

- **Severity:** Low 1.3 (`AV:L/AC:M/Au:M/C:P/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:** 22 Jul 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-j676-8v7f-r85c

## What is CVE-2015-5464?

CVE-2015-5464 is a low-severity vulnerability in n/a, published on 22 Jul 2015. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Gemalto SafeNet Luna HSM allows remote authenticated users to bypass intended key-export restrictions by leveraging (1) crypto-user or (2) crypto-officer access to an HSM partition.

Weakness: CWE-284 (Improper Access Control)

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

It affects 3 products.


Products: Gemalto Safenet Luna G5, Gemalto Safenet Luna Pci-E, Gemalto Safenet Luna Sa.

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

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

## Is CVE-2015-5464 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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