# CVE-2017-12820: Memory corruption in Gemalto's HASP SRM, Sentinel HASP and Sentinel LDK products prior to Sentinel LDK RTE

> Arbitrary memory read in Sentinel LDK allows remote attackers to cause a denial of service via controlled memory pointers.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Oct 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-m534-2jxx-fvmm

## What is CVE-2017-12820?

CVE-2017-12820 is a high-severity memory corruption vulnerability in Gemalto's HASP SRM, Sentinel HASP and Sentinel LDK products prior to Sentinel LDK RTE, published on 3 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Arbitrary memory read from controlled memory pointer in Gemalto's HASP SRM, Sentinel HASP and Sentinel LDK products prior to Sentinel LDK RTE version 7.55 leads to remote denial of service.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2017-12820?

It affects 1 product.


Products: Sentinel Sentinel Ldk Rte Firmware.

## How do I fix CVE-2017-12820?

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

## Is CVE-2017-12820 being exploited?

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

## Other vulnerabilities in Gemalto's HASP SRM, Sentinel HASP and Sentinel LDK products prior to Sentinel LDK RTE

- [CVE-2017-12822](https://insights.sbomify.com/CVE-2017-12822/): Missing authorization in Gemalto's HASP SRM, Sentinel HASP and Sentinel LDK products prior to Sentinel LDK RTE (critical 9.9)
- [CVE-2017-12819](https://insights.sbomify.com/CVE-2017-12819/): Auth bypass in Gemalto's HASP SRM, Sentinel HASP and Sentinel LDK products prior to Sentinel LDK RTE (critical 9.8)
- [CVE-2017-12821](https://insights.sbomify.com/CVE-2017-12821/): Memory corruption in Gemalto's HASP SRM, Sentinel HASP and Sentinel LDK products prior to Sentinel LDK RTE version 7.55 might cause remote code execution. (critical 9.8)
- [CVE-2017-12818](https://insights.sbomify.com/CVE-2017-12818/): Denial of service in Gemalto's HASP SRM, Sentinel HASP and Sentinel LDK products prior to Sentinel LDK RTE (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-12820 and fix it if it is affected.

What it is: CVE-2017-12820 is a high-severity memory corruption vulnerability in Gemalto's HASP SRM, Sentinel HASP and Sentinel LDK products prior to Sentinel LDK RTE, published on 3 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-12820 in the wild and no public exploit code.

Affected product: Gemalto's HASP SRM, Sentinel HASP and Sentinel LDK products prior to Sentinel LDK RTE. 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-2017-12820/ (Markdown: https://insights.sbomify.com/CVE-2017-12820/index.md)
```

## Sources

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

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