CVE-2018-17901
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, when processing project files the application fails to sanitize user input prior to performing write operations on a stack object, which may allow an attacker to execute code under the current 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 · high confidenceLAquis SCADA versions 4.1.0.3870 and prior contain a stack-based buffer overflow vulnerability when processing project files. The application fails to sanitize user-supplied input before performing write operations on a stack object, allowing an attacker to achieve code execution under the current 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.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
- 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.
-
Check LAquis SCADA versionLocate the LAquis SCADA executable (typically named laquis.exe or similar in the installation directory). Right-click the file, select Properties, and view the Version tab to find the File Version or Product Version.Affected if The version number displayed is 4.1.0.3870 or any lower version number (e.g., 4.1.0.3800, 4.0.x.x, etc.)
-
Verify application binary version via command lineOpen a command prompt, navigate to the LAquis installation directory, and run 'dir /a laquis.exe' to list the file. Then use 'wmic datafile where name="C:\path\to\laquis.exe" get version' to retrieve the version programmatically.Affected if The returned version string is 4.1.0.3870 or earlier.
-
Confirm project file handling is accessibleIdentify whether the LAquis application can load project files (typically .laq or similar project file extensions) by checking the application directory for existing project files or checking if the file open dialog accepts these files.Affected if Project files can be opened and loaded by the application, meaning a malicious project file could be processed by the vulnerable code path.
-
Check for untrusted project file sourcesReview the environment for any location where untrusted or externally-sourced project files could be placed into directories the SCADA application accesses, including network shares, removable media, or download folders.Affected if The SCADA system loads project files from locations accessible to untrusted users or processes.
If the installed LAquis SCADA version is 4.1.0.3870 or lower and the application loads project files from accessible locations, the environment is potentially affected by this buffer overflow 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 dataIf a vendor patch is available, update to the patched version immediately. Otherwise, restrict access to the application and project files to trusted personnel only and isolate the SCADA system from untrusted networks to reduce attack surface.
- Consultation4.0 h
- Implementation2.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-17901 — 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-17901 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