dbcve.org
Laquis ScadaApplication · Lcds

CVE-2018-18996

CRITICAL · 9.8 CVSS v3.0 Published 2019-02-05
Fix available
A fix is available. Upgrade to 4.1.0.4150 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
LCDS Laquis SCADA prior to version 4.1.0.4150 allows taking in user input without proper authorization or sanitation, which may allow an attacker to execute remote code on the server.

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 confidence

LCDS Laquis SCADA versions prior to 4.1.0.4150 contain an input validation vulnerability that allows unauthenticated attackers to inject malicious input, leading to remote code execution on the SCADA server. The lack of proper authorization checks and input sanitization on user-supplied data creates a critical attack surface exploitable over the network.

MitigationUpgrade Laquis SCADA to version 4.1.0.4150 or later. If immediate patching is not feasible, restrict network access to the SCADA interface using network segmentation and firewall rules to limit exposure to trusted assets only.

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
Laquis ScadaApplication
Affected:< 4.1.0.4150

CVSS 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
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Laquis SCADA installation version
    Locate the Laquis SCADA installation directory and check the executable or DLL version metadata, or check the Windows Programs and Features list for the installed version
    Affected if The installed version is lower than 4.1.0.4150
  2. Verify SCADA service exposure
    Check network listener configuration or firewall rules to determine if the SCADA service port (typically TCP ports associated with Laquis) is exposed to untrusted networks
    Affected if The SCADA interface is accessible from untrusted network segments or the internet
  3. Confirm remote access is enabled
    Inspect Laquis SCADA configuration files or service settings to verify if remote/client connections are enabled
    Affected if Remote connections are permitted and the service is listening on network interfaces
  4. Check authentication configuration
    Review Laquis SCADA security settings to determine if authentication is required for remote access
    Affected if Authentication is disabled or weak authentication is configured for remote clients

A system is affected if it runs Laquis SCADA version below 4.1.0.4150 and has the SCADA interface exposed to untrusted network access without proper authentication controls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 4.1.0.4150 or later
Fixed in 4.1.0.4150
Interim mitigation

Upgrade Laquis SCADA to version 4.1.0.4150 or later. If immediate patching is not feasible, restrict network access to the SCADA interface using network segmentation and firewall rules to limit exposure to trusted assets only.

Recommended fix Moderate confidence

Laquis SCADA 4.1.0.4150 or later

  1. Create a complete backup of the Laquis SCADA system, including configuration files and project data
  2. Download Laquis SCADA version 4.1.0.4150 or later from the official LCDS vendor website or authorized distribution channel
  3. Stop the Laquis SCADA service/application before beginning the upgrade process
  4. Install the updated Laquis SCADA version 4.1.0.4150 on the server, following the vendor's standard installation procedures
  5. After installation completes, start the Laquis SCADA service
  6. Verify the installation was successful by confirming the software version displays as 4.1.0.4150 or later
  7. Test critical SCADA functions to ensure normal operation after the upgrade
  8. Review system logs for any errors or warnings related to the upgrade
Caveat Test the upgrade in a non-production environment before deploying to production, as SCADA system behavior may change with version upgrades

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Laquis Scada Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-18996 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-18996 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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