CVE-2018-16165
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 · uneditedCross-site scripting vulnerability in LogonTracer 1.2.0 and earlier allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.
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 confidenceLogonTracer versions 1.2.0 and earlier contain a cross-site scripting (XSS) vulnerability that allows remote attackers to inject arbitrary JavaScript or HTML into web pages served by the application. The vulnerability stems from insufficient input sanitization or output encoding of user-supplied data rendered in the application's web 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<= 1.2.0CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Locate LogonTracer installation directorySearch for LogonTracer installation folders (commonly /opt/logontracer, /usr/share/logontracer, or a custom installation path). Check for a version file or examine the main script/module for a version string.Affected if LogonTracer is found on the system
-
Determine installed LogonTracer versionOpen the version file or the main Python script and locate the version declaration. Compare it to the affected range: versions 1.2.0 and earlier.Affected if The installed version is 1.2.0 or lower
-
Verify web interface is accessibleCheck if the LogonTracer web service is running (default port 8080 or configured port). Use 'netstat -tuln | grep <port>' or attempt a local HTTP request to confirm the web interface responds.Affected if The web interface is exposed and responds to HTTP requests
-
Confirm user input fields exist in web UIAccess the LogonTracer web interface and identify fields that accept user-supplied data (such as username, hostname, or search fields) which could potentially render without proper encoding.Affected if User-facing input fields are present in the web interface
You are affected if LogonTracer version 1.2.0 or earlier is installed AND its web interface is accessible, as user-supplied input in the web pages may not be properly sanitized.
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 dataUpgrade LogonTracer to a version newer than 1.2.0. Until an official patch is available, implement output encoding and input validation on all user-facing fields to prevent script injection.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-16165 — 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-16165 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