CVE-2018-19002
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 improper control of generation of code when opening a specially crafted project file, which may allow remote code execution, data exfiltration, or cause a system crash.
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 confidenceLCDS Laquis SCADA versions prior to 4.1.0.4150 contain a vulnerability where specially crafted project files are parsed with improper control of code generation, potentially allowing arbitrary code execution, data exfiltration, or denial of service on the host system.
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
- High
- Availability
- High
CVSS:3.0/AV:L/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.
-
Verify Laquis SCADA installationCheck common installation paths such as C:\Program Files\Lcds\Laquis or C:\Program Files (x86)\Lcds\Laquis, or search for laquis.exe on the systemAffected if The executable is found on the system
-
Identify installed Laquis SCADA versionRight-click on laquis.exe, select Properties, and check the File Version tab, or launch Laquis and look for the version in the application title bar or Help > AboutAffected if The version number displayed is lower than 4.1.0.4150
-
Confirm project file handling is in useCheck for .lqs project files on the system or within recent documents, which Laquis SCADA uses as its project file formatAffected if The system has .lqs project files that could be opened by Laquis SCADA
-
Check for recent Laquis project file activityReview the Windows Recent Items folder or application logs for recently opened .lqs files, which are the attack vector for this vulnerabilityAffected if Users have opened or are expected to open Laquis project files from potentially untrusted sources
A system is affected if Laquis SCADA is installed with a version number below 4.1.0.4150 and users open or could open project files, since the vulnerability triggers during project file parsing.
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. Additionally, implement file origin controls and only open project files from trusted, verified sources.
- Consultation2.0 h
- Implementation2.0 h
- Testing6.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 $3,232.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-19002 — 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-19002 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