dbcve.org
Sentinel Ldk Rte FirmwareOperating system · Sentinel

CVE-2017-12819

CRITICAL · 9.8 CVSS v3.0 Published 2017-10-04
Fix available
A fix is available. Upgrade to after 7.50 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
Remote manipulations with language pack updater lead to NTLM-relay attack for system user in Gemalto's HASP SRM, Sentinel HASP and Sentinel LDK products prior to Sentinel LDK RTE version 7.55.

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

A vulnerability in the language pack updater component of Gemalto's HASP SRM, Sentinel HASP and Sentinel LDK licensing products allows remote attackers to perform NTLM-relay attacks, potentially compromising system-level privileges. The vulnerability has a CVSS score of 9.8 (Critical), indicating severe risk of complete system compromise.

MitigationUpdate to Sentinel LDK RTE version 7.55 or later. If immediate patching is not feasible, restrict network access to the language pack updater and implement SMB signing to mitigate NTLM-relay attacks.

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 Rte FirmwareOperating system
Affected:<= 7.50

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.0/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. Identify if Sentinel LDK or HASP licensing software is installed
    Check for installed software named 'Sentinel LDK', 'HASP SRM', 'Sentinel HASP' or 'Sentinel LDK RTE' in system programs or services
    Affected if The software is present on the system
  2. Determine the installed version of Sentinel LDK RTE
    Locate the installed Sentinel LDK software and check its version property or check version via installed programs list, registry entries, or the haspdinst.exe /info output
    Affected if The version is 7.50 or earlier (any version <= 7.50)
  3. Verify if the language pack updater component is running
    Check for running services or processes related to 'hasplmd', 'haspd', 'Sentinel LDK License Manager' or port 1947 which is commonly used by the language pack updater
    Affected if The language pack updater service is active and listening on network ports
  4. Assess network exposure of the licensing service
    Review firewall rules and network configuration to determine if the Sentinel licensing service ports (commonly 1947, 475, 1947/TCP) are exposed to untrusted networks
    Affected if The licensing service is accessible from untrusted or external networks
  5. Check for NTLM authentication settings
    Review NTLM authentication configuration on the host to understand if NTLM relay attacks would be possible on the affected service
    Affected if NTLM authentication is allowed without SMB signing enforcement

The environment is affected if Sentinel LDK RTE version 7.50 or earlier is installed with the language pack updater component running and network-accessible.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 7.50
Interim mitigation

Update to Sentinel LDK RTE version 7.55 or later. If immediate patching is not feasible, restrict network access to the language pack updater and implement SMB signing to mitigate NTLM-relay attacks.

Recommended fix High confidence

Sentinel LDK RTE version 7.55

  1. Identify all systems running Sentinel LDK RTE with firmware version 7.50 or earlier
  2. Obtain Sentinel LDK RTE version 7.55 or later from the official Gemalto/Sentinel vendor website
  3. Test the upgrade in a non-production/staging environment to verify compatibility
  4. Schedule a maintenance window following change management procedures
  5. Apply the firmware upgrade to production systems running the affected Sentinel LDK products
  6. Verify the installed version is 7.55 or later using the system's version check mechanism
  7. Confirm the language pack updater functionality is operating normally after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sentinel Ldk Rte Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-2017-12819 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