dbcve.org
Lobby TrackApplication · Jollytech

CVE-2018-17482

MEDIUM · 5.5 CVSS v3.0 Published 2019-03-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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
Lobby Track Desktop could allow a local attacker to obtain sensitive information, caused by an error in Reports while in kiosk mode. By visiting the kiosk and clicking on reports, an attacker could exploit this vulnerability to gain access to all visitor records and obtain sensitive information.

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 confidence

Lobby Track Desktop exposes sensitive visitor records through the Reports feature even when operating in kiosk mode. The kiosk mode intended to restrict user access fails to properly enforce access controls, allowing any user who can access the kiosk interface to view all visitor records and associated sensitive information.

MitigationImplement proper authorization checks in kiosk mode to restrict access to the Reports feature, or disable the Reports functionality entirely when in kiosk mode. Consider adding role-based access controls or removing the Reports link from the kiosk interface.

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
Lobby TrackApplication
Affected:= 8.2.186

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/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 checks

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

  1. Confirm Lobby Track Desktop installation
    Check for Lobby Track Desktop application on the system - look for the executable or installation directory (commonly in Program Files or Program Files (x86) folder under a Jollytech or Lobby Track folder)
    Affected if The application is installed on the system
  2. Identify installed version
    Right-click the Lobby Track Desktop executable, select Properties, and check the Version tab, or look at the About/Help section within the application
    Affected if The installed version is exactly 8.2.186 as listed in the affected versions
  3. Verify kiosk mode configuration
    Access the application settings or administration panel and check whether kiosk mode is enabled - this is typically found in Security Settings, Access Control, or Kiosk Settings configuration area
    Affected if Kiosk mode is currently enabled on the system
  4. Check Reports feature accessibility
    In the kiosk interface (while in kiosk mode), locate and attempt to access the Reports feature or link - observe whether the Reports section is visible and accessible to the kiosk user
    Affected if The Reports feature or link is visible and accessible within the kiosk mode interface
  5. Confirm data exposure in Reports
    Within the Reports feature accessed via kiosk mode, verify whether visitor records, visitor logs, or sensitive visitor information is displayed without requiring additional authentication
    Affected if Sensitive visitor records and associated personal information are displayed without proper authorization when accessed through kiosk mode

A user is affected if they have Lobby Track Desktop version 8.2.186 installed with kiosk mode enabled, and the Reports feature is accessible in kiosk mode exposing visitor data that should be restricted.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization checks in kiosk mode to restrict access to the Reports feature, or disable the Reports functionality entirely when in kiosk mode. Consider adding role-based access controls or removing the Reports link from the kiosk interface.

Fix this in Lobby Track Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-17482 — 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-2018-17482 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