CVE-2018-17487
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 · uneditedLobby Track Desktop could allow a local attacker to gain elevated privileges on the system, caused by an error in the printer dialog. By visiting the kiosk and signing in as a visitor, an attacker could exploit this vulnerability using the command line to break out of kiosk mode.
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 · moderate confidenceLobby Track Desktop contains a privilege escalation vulnerability in its printer dialog functionality. An attacker with physical access to the kiosk can sign in as a visitor and use command line interaction through the printer dialog to escape kiosk mode restrictions and gain elevated privileges on the system.
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= 8.2.186CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Lobby Track Desktop versionOpen Windows Control Panel > Programs and Features, or check Add/Remove Programs. Look for 'Lobby Track Desktop' in the installed programs list and note the version number shown.Affected if The installed version is exactly 8.2.186.
-
Verify printer dialog is accessibleLaunch Lobby Track Desktop and attempt to access the printer or print dialog feature. This is typically found under File > Print or a printer icon in the application toolbar.Affected if The printer dialog opens and accepts input or command-line parameters.
-
Confirm kiosk mode configurationCheck if the system is configured to run Lobby Track Desktop in kiosk mode. Look for kiosk-specific startup parameters or dedicated kiosk software configuration.Affected if The application is running in a locked-down kiosk mode without full administrator controls.
-
Assess physical access controlsInspect the physical environment of the kiosk endpoint. Determine if the system is in a public or unsecured area where unauthorized individuals could gain hands-on access.Affected if The kiosk is accessible to untrusted users or visitors without direct supervision.
-
Check for command execution restrictionsAttempt to execute system commands through the printer dialog or verify if command prompt (cmd.exe) is accessible or blocked within the application context.Affected if Command execution is possible through the printer dialog interface or the system lacks application whitelisting and command-prompt restrictions.
A user is affected if their installed version of Lobby Track Desktop is exactly 8.2.186, the printer dialog feature is accessible, and the system runs in kiosk mode with insufficient restrictions on physical access and command execution.
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 dataApply vendor patch when available; additionally, implement application whitelisting, disable command prompt access in kiosk mode, and restrict physical access to the kiosk endpoint.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-17487 — 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-2018-17487 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