CVE-2021-32975
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 SP5) lacks proper validation of user-supplied data when parsing project files. This could lead to an out-of-bounds read. An attacker could leverage this vulnerability to execute code in the context of the current process.
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 confidenceCscape versions prior to 9.90 SP5 fail to validate user-supplied data when parsing project files, leading to an out-of-bounds read condition. This memory corruption vulnerability can be triggered by opening a malicious project file, allowing attackers to achieve code execution within the context of the running process.
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
- 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 Cscape is installedCheck the system for Hornerautomation Cscape installation by looking in Program Files (e.g., C:\Program Files\Horner Automation\Cscape) or using 'Add or Remove Programs'Affected if Cscape is installed on the system
-
Determine the installed Cscape versionLocate the executable (typically Cscape.exe) and check its file properties, or look in the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for Cscape entryAffected if The version shown is 9.90 or lower (any version below 9.90 SP5)
-
Verify the exact version numberOpen the Cscape application and check 'Help > About' or right-click the Cscape.exe file and select 'Properties' > 'Details' to view the Product VersionAffected if The version is 9.90 SP5 or lower (the vulnerability affects versions up to and including 9.90)
-
Check for recent project file operationsReview recent activity logs or monitor for .csp project file openings; the vulnerability is triggered when a malicious project file is openedAffected if Any project file has been opened in Cscape versions 9.90 or below
A system is affected if Hornerautomation Cscape version 9.90 or lower is installed and has been used to open project files, since the vulnerability requires parsing a malicious project file to trigger the out-of-bounds read.
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 · scoped9.90
Upgrade to Cscape version 9.90 SP5 or later. Until then, exercise caution when opening project files from untrusted sources.
Cscape 9.90 SP5 or later
- 1. Identify the current version of Cscape installed on the system
- 2. Download Cscape version 9.90 SP5 or later from the official vendor source
- 3. Uninstall the current version of Cscape or ensure all instances are closed
- 4. Install the downloaded Cscape 9.90 SP5 or later version
- 5. Verify the installed version matches or exceeds 9.90 SP5
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-32975 — 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-32975 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