CVE-2018-18990
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 · uneditedLCDS Laquis SCADA prior to version 4.1.0.4150 allows a user-supplied path in file operations prior to proper validation. An attacker can leverage this vulnerability to disclose sensitive information under the context of the web server process.
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 confidenceA path traversal vulnerability in LCDS Laquis SCADA versions prior to 4.1.0.4150 allows attackers to manipulate user-supplied file paths in file operations due to insufficient validation, potentially exposing sensitive system files under the web server process context.
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.4150CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Laquis SCADA installationCheck for Laquis SCADA installation by searching for the Laquis program folder in standard installation directories (e.g., C:\Program Files\LCDS\Laquis or C:\Laquis) or verify the service is running on the system.Affected if Laquis SCADA software is present on the system.
-
Identify installed Laquis SCADA versionLocate the version information in the Laquis installation directory. Check the main executable file properties (right-click on Laquis.exe, view Details) or look for a version file in the installation folder.Affected if Unable to determine version or version is below 4.1.0.4150.
-
Verify web server component is enabledConfirm whether the Laquis web server or HTTP interface component is enabled. This is typically configured in the Laquis configuration settings or service management console.Affected if The web server component is active and accessible, as the vulnerability manifests through web-facing file operations.
-
Check for external exposure of web servicesDetermine if the Laquis web server is bound to external network interfaces or accessible from untrusted networks, rather than only localhost or internal networks.Affected if The HTTP service is exposed to external or untrusted networks.
If Laquis SCADA version is present and below 4.1.0.4150 with the web server component enabled and accessible, the environment is likely affected by this path traversal vulnerability.
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 data4.1.0.4150
Upgrade to Laquis SCADA version 4.1.0.4150 or later which contains the fix for proper path validation. If immediate upgrading is not feasible, implement strict input validation on file path parameters and restrict file system permissions.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-18990 — 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-18990 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