CVE-2018-18998
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 uses hard coded credentials, which may allow an attacker unauthorized access to the system with high privileges.
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 confidenceThe LCDS Laquis SCADA software contains hardcoded credentials embedded in the codebase that provide high-privilege access to the system. An attacker with knowledge of these credentials can authenticate without authorization and gain administrative control over the SCADA environment.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Laquis SCADA installationCheck system for Laquis SCADA software by looking in Program Files for 'Laquis' folder, or check Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for Laquis entryAffected if Laquis SCADA software is found on the system
-
Determine installed versionLocate the Laquis executable (usually Laquis.exe) and right-click to view Properties, or launch Laquis and check About/Version information in the application interfaceAffected if Version is below 4.1.0.4150
-
Check for default administrative accountsReview Laquis configuration files (typically in the Laquis installation directory with .cfg or .xml extension) for hardcoded username and password entries used for administrative accessAffected if Default administrative credentials are found in configuration files or application settings
-
Verify network accessibilityCheck if the Laquis SCADA server port (commonly port 20014/tcp or configured port) is listening on network interfaces and accessible from other systemsAffected if SCADA interface is exposed to network without proper access controls
A user is affected if Laquis SCADA version below 4.1.0.4150 is installed and the hardcoded credentials can be used to gain unauthorized administrative access.
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.
dbcve · scoped4.1.0.4150
Update Laquis SCADA to version 4.1.0.4150 or later which removes the hardcoded credentials. Immediately change any default passwords, implement credential management policies, and restrict network access to the SCADA system.
4.1.0.4150 or later
- Download Laquis SCADA version 4.1.0.4150 or later from the official LCDS vendor website
- Back up the current Laquis SCADA installation, configuration files, and any project databases
- Install the updated version following the vendor's standard installation procedures
- After completing the upgrade, change all default credentials to strong, unique passwords for all user accounts
- Verify the upgrade was successful by checking the software version in the About or System Information section
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation12.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 $9,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-18998 — 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-18998 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