CVE-2023-32281
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 · uneditedThe affected application lacks proper validation of user-supplied data when parsing project files (e.g., CSP). This could lead to an out-of-bounds read in the FontManager. An attacker could leverage this vulnerability to execute arbitrary 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 confidenceThe application fails to validate user-supplied data when parsing project files (specifically CSP files), leading to an out-of-bounds read vulnerability in the FontManager component. This memory corruption can be leveraged to achieve arbitrary code execution within the context of the current 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= 4.70CVSS 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.
-
Check if Cscape is installedLocate and examine the Hornerautomation Cscape installation. Use system inventory tools or check common program directories for Cscape.exe, then right-click the executable and view Properties to find the version number.Affected if The installed version is exactly 9.90 (or a version that matches the affected range using '=' notation)
-
Check if Cscape Envisionrv is installedLocate and examine the Hornerautomation Cscape Envisionrv installation. Use system inventory tools or check common program directories for Envisionrv.exe, then right-click the executable and view Properties to find the version number.Affected if The installed version is exactly 4.70 (or a version that matches the affected range using '=' notation)
-
Confirm FontManager component presenceInspect the Cscape installation directory for files related to FontManager, such as FontManager.dll or similar font handling libraries that are used during CSP file parsing.Affected if The FontManager component exists and is used by the application for parsing CSP files
-
Verify CSP project file parsing capabilityOpen a CSP project file with the installed Cscape application. This triggers the vulnerable parsing code path in the FontManager component.Affected if The application can open and parse CSP files, which invokes the vulnerable FontManager file parsing logic
A user is affected if they have Cscape version 9.90 or Cscape Envisionrv version 4.70 installed and can open CSP project files, which triggers the vulnerable FontManager component during parsing.
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-provided patches addressing input validation in the FontManager file parsing logic. Until patched, avoid opening untrusted CSP project files with the affected application.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-32281 — 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-2023-32281 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