CVE-2018-18994
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 an out of bounds read when opening a specially crafted project file, which may cause a system crash or allow data exfiltration.
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 confidenceAn out-of-bounds read vulnerability exists in LCDS Laquis SCADA software when parsing specially crafted project files. The vulnerability allows attackers to read memory beyond allocated buffers, potentially causing denial-of-service conditions through system crashes or enabling unauthorized data exfiltration.
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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/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.
-
Verify Laquis SCADA installationLook for Laquis SCADA in the program files directory (typically C:\Program Files\LCDS\Laquis SCADA or C:\Program Files (x86)\LCDS\Laquis SCADA) or check for Laquis SCADA entry in Add/Remove Programs.Affected if Laquis SCADA software is found on the system
-
Identify installed version numberOpen the Laquis SCADA application and navigate to Help > About, or check the version displayed on the main window. Alternatively, right-click the Laquis SCADA executable in the installation folder, select Properties, and view the File Version field.Affected if The displayed version is lower than 4.1.0.4150
-
Confirm version matches vulnerable rangeCompare your identified version against the affected range: any version before 4.1.0.4150 is vulnerable. Versions 4.1.0.4150 and later are patched.Affected if Installed version is less than 4.1.0.4150
-
Check for project file handling exposureLaquis SCADA loads project files (.lqp or proprietary project formats) when opened. Determine if the system handles project files from external or untrusted sources, as this is the attack vector for the out-of-bounds read vulnerability.Affected if The vulnerable version (< 4.1.0.4150) is installed AND the software processes project files
You are affected if Laquis SCADA version less than 4.1.0.4150 is installed and the software is used to open project files.
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 Laquis SCADA to version 4.1.0.4150 or later to remediate the vulnerability. Until patched, avoid opening project files from untrusted sources.
- Consultation6.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 $7,296.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-18994 — 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-18994 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