# CVE-2021-32928: Misconfiguration in Sentinel LDK Run-Time Environment

> The Sentinel LDK uninstaller fails to remove a firewall rule, leaving TCP port 1947 open to private networks after removal.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jun 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-pc4g-vw4w-2pmh

## What is CVE-2021-32928?

CVE-2021-32928 is a critical vulnerability in Sentinel LDK Run-Time Environment, published on 16 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Sentinel LDK Run-Time Environment installer (Versions 7.6 and prior) adds a firewall rule named “Sentinel License Manager” that allows incoming connections from private networks using TCP Port 1947. While uninstalling, the uninstaller fails to close Port 1947.

Weakness: CWE-459 (Incomplete Cleanup)

## Which versions are affected by CVE-2021-32928?

It affects 1 product.


Products: Thalesgroup Sentinel Ldk Run-Time Environment.

## How do I fix CVE-2021-32928?

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

## Is CVE-2021-32928 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-32928 and fix it if it is affected.

What it is: CVE-2021-32928 is a critical vulnerability in Sentinel LDK Run-Time Environment, published on 16 Jun 2021. 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-2021-32928 in the wild and no public exploit code.

Affected product: Sentinel LDK Run-Time Environment. 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-2021-32928/ (Markdown: https://insights.sbomify.com/CVE-2021-32928/index.md)
```

## Sources

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

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