dbcve.org
CscapeApplication · Hornerautomation

CVE-2022-3379

HIGH · 7.8 CVSS v3.1 Published 2022-10-27
Fix available
A fix is available. Upgrade to 9.90 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
Horner Automation's Cscape version 9.90 SP7 and prior does not properly validate user-supplied data. If a user opens a maliciously formed FNT file, then an attacker could execute arbitrary code within the current process by writing outside the memory buffer.

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 confidence

A buffer overflow vulnerability exists in Horner Automation Cscape version 9.90 SP7 and prior when parsing FNT font files. The software fails to properly validate user-supplied data, allowing an attacker to write outside memory buffer boundaries and achieve arbitrary code execution within the current process.

MitigationApply vendor patches or upgrade Cscape beyond version 9.90 SP7. Until patched, avoid opening FNT files from untrusted sources.

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
CscapeApplication
Affected:< 9.90= 9.90

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the installed Cscape application
    Search for Cscape executable in Program Files (typically C:\Program Files\Horner Automation\Cscape or C:\Program Files (x86)\Horner Automation\Cscape). Check the file properties of Cscape.exe to view the version number.
    Affected if The version shown is 9.90 or any version prior to 9.90 SP7 (such as 9.90 SP1-SP6, 9.80, 9.70, etc.)
  2. Confirm the exact version and service pack
    Right-click the Cscape.exe file, select Properties, then view the Details tab. Note the File Version field which typically includes the SP (Service Pack) designation (e.g., 9.90.0.0).
    Affected if The version reads exactly 9.90 or indicates any service pack version prior to SP7 (9.90 SP1 through SP6)
  3. Identify FNT font files in use or storage
    Search the system for .FNT files, particularly in project directories, recent files locations, or any folder where Cscape projects are stored. Common paths include Documents\Cscape or project-specific folders.
    Affected if Any FNT font files exist in the environment that could be opened or processed by Cscape
  4. Check for recent Cscape project activity
    Review recent Cscape project files (.csp) to determine if the application has been used to open or parse font-related resources. Look for references to custom fonts within project configurations.
    Affected if Projects reference custom FNT font files or the software has been used to import/parse font resources from external FNT files

You are affected if Cscape version 9.90 or any version prior to 9.90 SP7 is installed and FNT font files can be opened or processed by the software.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 9.90 or later
Fixed in 9.90
Interim mitigation

Apply vendor patches or upgrade Cscape beyond version 9.90 SP7. Until patched, avoid opening FNT files from untrusted sources.

Recommended fix Moderate confidence

Latest available Cscape version (greater than 9.90) from Horner Automation

  1. Download the latest version of Cscape from Horner Automation's official website or trusted distribution channel
  2. Prior to upgrade, back up any existing Cscape projects and configurations
  3. Close any running instances of Cscape
  4. Install the newer version of Cscape (version greater than 9.90)
  5. Verify the installation completed successfully
  6. Avoid opening untrusted or unknown FNT files in Cscape to reduce exposure to similar file-parsing vulnerabilities
Caveat Review release notes for any changes to project file compatibility or deprecated features when upgrading major versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cscape Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-3379 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-3379 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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