CVE-2021-22682
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 · uneditedCscape (All versions prior to 9.90 SP4) is configured by default to be installed for all users, which allows full permissions, including read/write access. This may allow unprivileged users to modify the binaries and configuration files and lead to local privilege escalation.
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 confidenceCscape versions prior to 9.90 SP4 default to an all-users installation with overly permissive file system ACLs, granting read/write access to all users on the system. This allows unprivileged users to modify executable binaries and configuration files in the installation directory, which can be leveraged for local privilege escalation when the software runs with elevated privileges.
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< 9.90= 9.90CVSS 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.1/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 Cscape installation directoryCheck common installation paths such as C:\Program Files\Hornerautomation\Cscape or C:\Program Files (x86)\Hornerautomation\Cscape, or search for the Cscape executable file on the systemAffected if Cscape is found installed on the system
-
Determine installed Cscape versionRight-click on the Cscape executable (typically Cscape.exe) in the installation folder, select Properties, and check the Details tab for the Product Version, or check the version in the application via Help > AboutAffected if The version displayed is prior to 9.90 or equals 9.90 (versions 9.90 SP4 and later are not affected)
-
Inspect ACLs on the Cscape installation folderRight-click the Cscape installation folder, select Properties > Security tab, and examine the permissions for each user or group listed. Verify whether users other than Administrators and System have Write or Modify permissionsAffected if Non-administrative users or the 'Users' group are granted Write or Modify access to the installation directory
-
Check ACLs on executable files in the installation folderRight-click on Cscape.exe and other executable files in the installation folder, select Properties > Security, and verify if standard users have Write permissionAffected if Standard users have Write permission to executable files in the installation directory
-
Verify if Cscape runs with elevated privilegesCheck if there are scheduled tasks, services, or shortcuts configured to run Cscape with 'Run as administrator' or elevated privileges, or examine shortcut properties for such settingsAffected if Cscape is configured to execute with elevated or administrative privileges while the installation directory remains writable by non-privileged users
The environment is affected if Cscape version 9.90 or prior is installed with default permissions that allow non-administrative users to write to the installation directory, especially if the software runs with elevated privileges.
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 data9.90
Upgrade to Cscape version 9.90 SP4 or later, which addresses the default permission misconfiguration; alternatively, manually restrict file system permissions on the installation directory to administrative-only access.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22682 — 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-22682 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