CVE-2018-17899
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 · uneditedLAquis SCADA Versions 4.1.0.3870 and prior has a path traversal vulnerability, which may allow remote code execution.
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 confidencePath traversal vulnerability in LAquis SCADA versions 4.1.0.3870 and prior allows attackers to access files outside the web root directory through specially crafted directory traversal sequences, potentially leading to remote code execution.
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<= 4.1.0.3870CVSS 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
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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.
-
Confirm LAquis SCADA installationLocate the LAquis SCADA installation directory, typically in C:\Program Files\LAquis or C:\Program Files (x86)\LAquis, and check the executable version properties or the application about dialog.Affected if The installed version is 4.1.0.3870 or any version prior to it.
-
Identify the installed version numberRight-click on the main executable (usually lcs.exe, lcd.exe, or laquis.exe) and select Properties, then view the Details tab to find the File Version. Alternatively, open the application and navigate to Help > About.Affected if The version displayed is 4.1.0.3870 or lower.
-
Determine if web server component is enabledCheck the LAquis SCADA project configuration files (.lcs or .xml files) for web server settings. Look for configuration keys such as EnableWebServer, WebServerPort, or similar settings that indicate the HTTP interface is active.Affected if The web server or HTTP interface component is enabled and configured to accept connections.
-
Verify network exposure of the web interfaceCheck system listening ports using netstat -an or by reviewing firewall rules. Look for ports typically used by LAquis web (often port 8081, 80, or configured custom ports). Determine if these ports are bound to external interfaces rather than localhost only.Affected if The web interface port is listening on 0.0.0.0 or an external IP address, making it network-accessible.
You are affected if LAquis SCADA version 4.1.0.3870 or lower is installed AND the web server component is enabled and exposed (either locally or over the network), as the path traversal vulnerability requires the HTTP interface to be accessible.
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 LAquis SCADA to a version newer than 4.1.0.3870. If upgrading is not immediately feasible, implement strict input validation on file access parameters and restrict file system access permissions to limit the impact of path traversal attacks.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-17899 — 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-17899 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