CVE-2023-32203
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 · uneditedHorner Automation Cscape lacks proper validation of user-supplied data when parsing project files (e.g., HMI). This could lead to an out-of-bounds write at CScape_EnvisionRV+0x2e374b. 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 · high confidenceHorner Automation Cscape fails to properly validate user-supplied data when parsing project files (e.g., .HMI files). This inadequate input validation enables an out-of-bounds write vulnerability at a specific memory address (CScape_EnvisionRV+0x2e374b), which an attacker can exploit to execute arbitrary code 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.
-
Identify installed Cscape versionCheck the program version by opening Horner Automation Cscape and navigating to Help > About, or locate the executable file in Program Files and view its propertiesAffected if The installed version is exactly 9.90 (exact version match)
-
Identify installed EnvisionRV versionCheck the EnvisionRV version through its Help > About menu, or locate the EnvisionRV executable in the installation directory and view file propertiesAffected if The installed version is exactly 4.70 (exact version match)
-
Verify project file parsing functionalityConfirm that the Cscape or EnvisionRV application can open and parse .HMI project files; this is the normal operating mode for these applicationsAffected if The application is capable of loading and parsing .HMI project files, which is the built-in functionality that triggers the vulnerability
-
Assess exposure to untrusted project filesDetermine whether the system routinely opens .HMI files from untrusted or external sources, or if there are mechanisms by which external parties could supply project files to the applicationAffected if The application is configured to process .HMI files from untrusted or unverified sources, creating an attack vector for the vulnerability
A system is affected if it runs Horner Automation Cscape version 9.90 or EnvisionRV version 4.70 and can be persuaded to open malicious .HMI project files.
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 dataAvoid opening untrusted or unverified Cscape project files; apply vendor patches from Horner Automation when available; implement network segmentation to limit exposure of affected systems.
- Consultation6.0 h
- Implementation12.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,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-32203 — 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-32203 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