Sentinel Ldk Run Time EnvironmentApplication · Thalesgroup

CVE-2021-32928

CRITICAL · 9.8 CVSS v3.1 Published 2021-06-16
Fix available
A fix is available. Upgrade to after 7.6 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Sentinel LDK Run-Time Environment installer (versions 7.6 and prior) creates a Windows firewall rule named 'Sentinel License Manager' that allows incoming TCP connections on port 1947 from private networks. During uninstallation, the uninstaller fails to remove this firewall rule, leaving port 1947 exposed and potentially allowing unauthorized remote access to the system.

MitigationAfter uninstalling Sentinel LDK Run-Time Environment, manually verify and remove the 'Sentinel License Manager' firewall rule and confirm port 1947 is no longer listening or exposed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Sentinel Ldk Run Time EnvironmentApplication
Affected:<= 7.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check for the Sentinel License Manager firewall rule
    Run 'netsh advfirewall firewall show rule name=all' or use PowerShell Get-NetFirewallRule -DisplayName 'Sentinel License Manager' to list all firewall rules and look for a rule named 'Sentinel License Manager'
    Affected if A firewall rule named 'Sentinel License Manager' exists that allows incoming TCP connections on port 1947 from private networks
  2. Verify if port 1947 is listening
    Run 'netstat -an | findstr :1947' or use PowerShell Get-NetTCPConnection -LocalPort 1947 to check if the system is listening on port 1947
    Affected if Port 1947 is in LISTENING state and accepting incoming TCP connections
  3. Check current Sentinel LDK installation status
    Check Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for Sentinel LDK entries, or run 'wmic product get name,version' to list installed software
    Affected if Sentinel LDK Run-Time Environment version 7.6 or prior is currently installed, or was previously uninstalled but the firewall rule persists
  4. Confirm the rule allows inbound traffic from private networks
    Run 'netsh advfirewall firewall show rule name="Sentinel License Manager"' and examine the LocalPort, Direction, and Profile settings
    Affected if The rule shows Direction=In, Action=Allow, and Profile includes Private networks with LocalPort=1947

The environment is affected if the 'Sentinel License Manager' firewall rule exists allowing TCP port 1947 from private networks, regardless of whether Sentinel LDK is currently installed or was uninstalled, because the uninstaller fails to remove this rule.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 7.6
Interim mitigation

After uninstalling Sentinel LDK Run-Time Environment, manually verify and remove the 'Sentinel License Manager' firewall rule and confirm port 1947 is no longer listening or exposed.

Fix this in Sentinel Ldk Run Time Environment Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-32928 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-32928 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data