CVE-2018-5463
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 · uneditedA structured exception handler overflow vulnerability in Leao Consultoria e Desenvolvimento de Sistemas (LCDS) LTDA ME LAquis SCADA 4.1.0.3391 and earlier may allow code execution.
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 confidenceA structured exception handler (SEH) overflow vulnerability in LAquis SCADA versions 4.1.0.3391 and earlier allows an attacker to overwrite the exception handler on the stack, potentially achieving code execution through controlled buffer overflow.
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.3391CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/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.
-
Locate LAquis SCADA installationSearch for the Laquis executable (commonly named laquis.exe or similar) in standard installation directories such as C:\Program Files\LAquis or C:\Program Files (x86)\LAquis, or check the program directory where the SCADA application was installed.Affected if The Laquis SCADA executable is found on the system
-
Identify installed version numberRight-click on the Laquis executable file, select Properties, then view the Details tab to find the Product Version. Alternatively, run 'wmic datafile where name="PATH_TO_EXECUTABLE" get Version' or use PowerShell to query file version info.Affected if The reported version is 4.1.0.3391 or any version lower than this
-
Confirm version matches vulnerable rangeCompare the identified version against the affected range: versions 4.1.0.3391 and earlier are vulnerable. Record the exact version number displayed in the file properties.Affected if The installed version number is less than or equal to 4.1.0.3391
-
Assess network exposureReview firewall rules and network configuration to determine if the LAquis SCADA service ports are exposed to external or untrusted networks. Check if the application listens on accessible network interfaces.Affected if The SCADA application is reachable from untrusted network segments or the internet
You are affected if LAquis SCADA is installed with version 4.1.0.3391 or earlier and the application is accessible to potential attackers.
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 dataApply vendor patch or upgrade to a patched version of LAquis SCADA; if no patch available, reduce attack surface through network segmentation and minimize exposure of the SCADA system to untrusted networks.
- Consultation8.0 h
- Implementation4.0 h
- Testing12.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 $7,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-5463 — 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-5463 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