CVE-2018-17486
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 bypass security restrictions, caused by an error in the find visitor function while in kiosk mode. By visiting the kiosk and selecting find visitor, an attacker could exploit this vulnerability to delete visitor records or remove a host.
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 confidenceLobby Track Desktop's kiosk mode contains an access control bypass in the find visitor function. An attacker with physical access to the kiosk can exploit improper authorization logic to delete visitor records or remove hosts, bypassing the intended security restrictions of kiosk mode.
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
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/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.
-
Confirm Lobby Track Desktop is installedCheck program files for Jollytech/Lobby Track installation directory, or look for Lobby Track in Add/Remove ProgramsAffected if Lobby Track Desktop software is present on the system
-
Identify installed versionRight-click the Lobby Track executable, select Properties, then Details tab to view File Version; alternatively check Add/Remove Programs for version 8.2.186Affected if Installed version is exactly 8.2.186
-
Check if kiosk mode is enabledLook for kiosk configuration settings in Lobby Track admin panel or configuration files, typically found in the program data or installation directoryAffected if Kiosk mode is configured and active on the system
-
Verify find visitor function accessibilityAccess the kiosk interface and attempt to locate the find visitor function; observe if unauthorized deletion of visitor records or host removal options are accessible without proper authenticationAffected if The find visitor function allows record deletion or host removal without additional authorization prompts in kiosk mode
-
Review kiosk mode access controlsIn kiosk settings, verify that the find visitor function is restricted and that authorization is required before allowing delete or remove host operationsAffected if The find visitor function permits delete/remove operations without requiring the expected authorization checks that kiosk mode should enforce
A system is affected if Lobby Track Desktop version 8.2.186 is installed with kiosk mode enabled, and the find visitor function allows deletion of visitor records or removal of hosts without proper authorization checks.
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 to fix the authorization bypass in the find visitor function within kiosk mode. Until patch is available, consider additional physical controls or monitoring on kiosk-accessible systems.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-17486 — 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-17486 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