CVE-2021-41579
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 through 4.3.1.1085 is vulnerable to a control bypass and path traversal. If an attacker can get a victim to load a malicious els project file and use the play feature, then the attacker can bypass a consent popup and write arbitrary files to OS locations where the user has permission, leading to 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 confidenceLCDS LAquis SCADA through 4.3.1.1085 contains a path traversal vulnerability in its .els project file parser. When a victim loads a crafted malicious .els file and activates the play feature, the application bypasses a consent popup and writes arbitrary files to OS locations where the user has write permissions, enabling code execution.
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.1.1085CVSS 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.1/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.
-
Identify if LAquis SCADA is installedLook for the LAquis SCADA application in Program Files, Program Files (x86), or the application directory. Check for executables named LAquis.exe, LAquisscada.exe, or similar naming patterns.Affected if LAquis SCADA software is found on the system
-
Determine the installed LAquis SCADA versionRight-click the LAquis executable, select Properties, and check the File Version or Product Version field. Alternatively, launch the application and look for version information in the About or Help menu.Affected if The installed version is 4.3.1.1085 or any version lower than this (the vulnerable range)
-
Check if .els project files exist in the environmentSearch for .els files on the system using File Explorer or command: dir /s /b *.els. Inspect common project directories where SCADA project files are stored.Affected if .els project files are present and the application loads them
-
Verify the play feature is accessibleOpen any existing .els project file in LAquis SCADA. Look for a Play button, Play menu item, or similar playback control in the application interface.Affected if The play feature is available and can be activated within the application
The environment is affected if LAquis SCADA version 4.3.1.1085 or lower is installed, the user works with .els project files, and the play feature is accessible, allowing a malicious crafted .els file to write arbitrary files when opened and played.
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 dataDo not open untrusted .els project files from unverified sources. Restrict user permissions to the minimum required for SCADA operations. Apply vendor patches when available.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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 $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-41579 — 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-2021-41579 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