Cx ProgrammerApplication · Omron

CVE-2023-22314

HIGH · 7.8 CVSS v3.1 Published 2023-08-03
Fix available
A fix is available. Upgrade to after 9.79 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
Use after free vulnerability exists in CX-Programmer Ver.9.79 and earlier. By having a user open a specially crafted CXP file, information disclosure and/or arbitrary code execution may occur. This vulnerability is different from CVE-2023-22277 and CVE-2023-22317.

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

Use-after-free vulnerability in CX-Programmer Ver.9.79 and earlier allows remote code execution or information disclosure via specially crafted CXP files. The vulnerability stems from improper memory management during file parsing, leading to a use-after-free condition that can be triggered when a user opens a malicious file.

MitigationUpgrade CX-Programmer to a version newer than 9.79. Until then, exercise caution when opening CXP 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
Cx ProgrammerApplication
Affected:<= 9.79

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 CX-Programmer installation
    Search for CX-Programmer in the system. Common installation paths include C:\Program Files\Omron\CX-Programmer or C:\Program Files (x86)\Omron\CX-Programmer. Check Start Menu for CX-Programmer shortcuts.
    Affected if CX-Programmer is installed on the system
  2. Identify installed CX-Programmer version
    Open CX-Programmer and navigate to Help > About CX-Programmer, or right-click the executable in the installation folder and select Properties > Details to view the File Version.
    Affected if The displayed version is 9.79 or lower (any version up to and including 9.79)
  3. Confirm vulnerability trigger condition
    Verify that the CX-Programmer installation can open CXP project files. The vulnerability is triggered when a user opens a specially crafted CXP file.
    Affected if Users can open CXP files in the installed version, meaning the parsing code with the use-after-free flaw is active

A user is affected if CX-Programmer version 9.79 or lower is installed and the software can open CXP files, as the vulnerability requires opening a malicious file to trigger the use-after-free condition.

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 a release after 9.79
Interim mitigation

Upgrade CX-Programmer to a version newer than 9.79. Until then, exercise caution when opening CXP files from untrusted sources.

Recommended fix Moderate confidence

CX-Programmer version greater than 9.79 (contact Omron for exact fixed release)

  1. 1. Visit the official Omron website or contact Omron support to obtain the latest version of CX-Programmer.
  2. 2. Download the CX-Programmer installer for the most recent stable release.
  3. 3. Before upgrading, back up any existing CX-Programmer projects (.cxp files) to prevent data loss.
  4. 4. Uninstall the current version of CX-Programmer (version 9.79 or earlier).
  5. 5. Install the new version of CX-Programmer.
  6. 6. Verify the installation by checking the software version in the application (Help > About CX-Programmer).
  7. 7. Test that existing projects open correctly in the new version.
Caveat Review Omron release notes for any changes to project file compatibility or deprecated features between versions

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

Fix this in Cx Programmer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-22314 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-22314 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