CVE-2020-10618
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 Versions 4.3.1 and prior. The affected product is vulnerable to sensitive information exposure by unauthorized users.
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 confidenceThe LAquis SCADA versions 4.3.1 and prior contain a vulnerability that allows unauthorized users to access sensitive information. This appears to be an improper access control issue where the system fails to adequately restrict or authenticate user access to potentially sensitive data, files, or system resources.
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.3.1CVSS 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
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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.
-
Identify LAquis SCADA versionLocate the installed LAquis SCADA application and retrieve its version number from the software properties, about dialog, or installation directoryAffected if The installed version is 4.3.1 or any version lower than 4.3.1
-
Determine network exposure of SCADA interfaceIdentify the network interfaces and ports the LAquis SCADA service is listening on, then verify which networks or IP ranges can reach those portsAffected if The SCADA interface is accessible from networks other than trusted, authorized internal networks
-
Verify access control configurationInspect the SCADA system's user authentication settings, anonymous access permissions, and any guest or default account configurationsAffected if Anonymous or unauthenticated access is permitted, or default credentials remain in use
-
Check for sensitive data exposureAttempt to access SCADA project files, configuration files, or data stores without providing credentials to confirm whether sensitive information can be retrievedAffected if Sensitive files, project data, or configuration information can be accessed without authentication
-
Review network segmentationExamine firewall rules, network ACLs, or VLAN assignments surrounding the SCADA system to determine if it is properly isolatedAffected if The SCADA system is not isolated behind network segmentation or is reachable from unauthorized network segments
You are affected if the installed LAquis SCADA version is 4.3.1 or prior AND the SCADA interface or its data stores are accessible from unauthorized network locations.
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 dataRestrict network access to the SCADA system to authorized personnel only, and apply any available vendor patches or updates to address the unauthorized information disclosure. If no patch exists, implement additional authentication layers and verify access controls on sensitive data stores.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10618 — 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-2020-10618 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