CVE-2019-8283
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 · uneditedHasplm cookie in Gemalto Admin Control Center, all versions prior to 7.92, does not have 'HttpOnly' flag. This allows malicious javascript to steal it.
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 confidenceThe Hasplm cookie in Gemalto Admin Control Center versions prior to 7.92 is missing the HttpOnly flag, allowing malicious JavaScript executed via cross-site scripting (XSS) to access and exfiltrate the cookie value.
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< 7.92CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Gemalto Admin Control Center is installedCheck for Sentinel Admin Control Center installation by looking for it in installed programs (Windows: Control Panel > Programs and Features, Linux: check package manager), or by accessing the web interface on typical ports 1947 or 8080 if the service is runningAffected if Gemalto Sentinel LDK Admin Control Center is installed and running
-
Determine the installed version of Sentinel LDKLog into the Admin Control Center web interface and look for the version information typically displayed in the About or Help section, or check the installed software version through the system package managerAffected if Version is lower than 7.92
-
Verify if the Hasplm cookie existsLog into the Admin Control Center web interface, open browser developer tools (F12), go to the Application/Storage tab, and examine cookies under the Admin Control Center domainAffected if The Hasplm cookie is present after authentication
-
Check if HttpOnly flag is set on Hasplm cookieIn browser developer tools, select the Hasplm cookie and examine its attributes. Alternatively, use a network proxy or curl to capture the Set-Cookie HTTP response header and verify whether the HttpOnly keyword is presentAffected if The Hasplm cookie exists but the HttpOnly attribute is missing from the cookie definition
User is affected if Gemalto Sentinel LDK version is below 7.92 and the Hasplm cookie lacks the HttpOnly flag, allowing XSS exploits to steal the session cookie
Generated from the published advisory. Verify against your own configuration.
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 data7.92
Upgrade Gemalto Admin Control Center to version 7.92 or later, which includes the HttpOnly flag on the Hasplm cookie to prevent client-side script access.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-8283 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-8283 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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