dbcve.org
Cx ProgrammerApplication · Omron

CVE-2022-21219

HIGH · 7.8 CVSS v3.1 Published 2022-03-10
Fix available
A fix is available. Upgrade to 9.77 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
Out-of-bounds read vulnerability in CX-Programmer v9.76.1 and earlier which is a part of CX-One (v4.60) suite allows an attacker to cause information disclosure and/or arbitrary code execution by having a user to open a specially crafted CXP file.

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 confidence

Out-of-bounds read vulnerability in CX-Programmer's CXP file parser allows attackers to read memory beyond buffer boundaries when users open specially crafted CXP files, potentially leaking sensitive information or achieving arbitrary code execution.

MitigationAvoid opening CXP files from untrusted sources; apply vendor patches when released for CX-Programmer v9.76.1 and earlier.

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
Cx ProgrammerApplication
Affected:< 9.77

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. Confirm CX-Programmer is installed
    Look for CX-Programmer in the list of installed applications on Windows (Add or Remove Programs, or Programs and Features), or search for the CX-Programmer executable in typical installation directories such as C:\Program Files\Omron\CX-Programmer
    Affected if CX-Programmer is present on the system
  2. Determine the installed CX-Programmer version
    Right-click the CX-Programmer executable (commonly found in C:\Program Files\Omron\CX-Programmer\CX-P.exe), select Properties, then go to the Details tab to view the File Version
    Affected if The displayed version is less than 9.77 (for example, 9.76.1, 9.76, 9.75, etc.)
  3. Verify the CXP file parsing feature is in use
    Check whether the system has any .cxp project files that have been opened or are stored locally, as the vulnerability triggers when CX-Programmer parses these files
    Affected if CXP files exist on the system and have been opened with CX-Programmer
  4. Check for recent CX-Programmer execution activity
    Review Windows Event Logs or the application's recent files list to see if CXP files from external or untrusted sources have been opened
    Affected if CXP files from potentially untrusted sources were opened with CX-Programmer

The environment is affected if CX-Programmer version 9.76.1 or earlier is installed and CXP files can be opened with it, as the out-of-bounds read occurs during CXP file parsing in those versions.

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.77 or later
Fixed in 9.77
Interim mitigation

Avoid opening CXP files from untrusted sources; apply vendor patches when released for CX-Programmer v9.76.1 and earlier.

Recommended fix High confidence

CX-Programmer version 9.77 or later (included in CX-One v4.60 or later)

  1. 1. Check the current version of CX-Programmer by opening the application and navigating to Help > About CX-Programmer
  2. 2. Download CX-Programmer version 9.77 or later from the official Omron website (or download the latest CX-One v4.60 suite which includes the fixed version)
  3. 3. Close CX-Programmer and any related CX-One applications
  4. 4. Run the installer for the updated version
  5. 5. Follow the installation wizard prompts to complete the update
  6. 6. Verify the installed version by checking Help > About CX-Programmer confirms version 9.77 or later

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

Fix this in Cx Programmer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-21219 — 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-21219 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