CVE-2023-38746
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 · uneditedOut-of-bounds read vulnerability/issue exists in CX-Programmer Included in CX-One CXONE-AL[][]D-V4 V9.80 and earlier. By having a user open a specially crafted CXP file, information disclosure and/or arbitrary code execution may occur.
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 confidenceAn out-of-bounds read vulnerability exists in CX-Programmer (part of CX-One suite) when parsing specially crafted CXP project files. The vulnerability occurs due to insufficient bounds checking during file parsing, allowing memory contents to be read beyond allocated buffers. This can lead to information disclosure and potentially arbitrary code execution when the attacker controls the memory layout.
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.80CVSS 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.
-
Locate CX-Programmer installationCheck Windows Programs and Features or look for the CX-One suite installation directory on the systemAffected if CX-Programmer from the CX-One suite is installed on the system
-
Determine installed CX-Programmer versionOpen CX-Programmer and access the About dialog to view the version number, or locate the main executable file and check its version property in the file detailsAffected if The displayed version number is 9.80 or lower (any version up to and including 9.80)
-
Identify the vulnerable componentThe vulnerability is triggered when CX-Programmer parses CXP project files. Check if the software is configured to open .cxp file extensions and review file association settingsAffected if CX-Programmer is used to open CXP project files
A system is affected if CX-Programmer version 9.80 or lower is installed and users can open CXP project files with the software, as the out-of-bounds read occurs during file 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.
dbcve · scopedUpdate CX-Programmer/CX-One to a version newer than V9.80. Until patched, avoid opening CXP files from untrusted sources.
CX-One CXONE-AL[][]D-V4 version newer than V9.80 (latest available version)
- 1. Visit the official Omron support page at www.ia.omron.com to obtain the latest version of CX-Programmer/CX-One
- 2. Download CX-One version newer than V9.80 that includes the security fix for CVE-2023-38746
- 3. Uninstall the current version of CX-Programmer/CX-One from the system
- 4. Install the updated CX-One version containing the patched CX-Programmer
- 5. Verify the installation by checking the program version (Help > About CX-Programmer)
- 6. Ensure all existing CXP project files are backed up before opening them in the updated software
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-38746 — 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-38746 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