CVE-2022-3396
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 · uneditedOMRON CX-Programmer 9.78 and prior is vulnerable to an Out-of-Bounds Write, which may allow an attacker to execute arbitrary code.
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 confidenceOMRON CX-Programmer versions 9.78 and prior contain an out-of-bounds write vulnerability. This memory corruption flaw allows an attacker to write data beyond allocated buffer boundaries, potentially achieving arbitrary code execution on the target system. The critical CVSS score of 9.8 indicates the vulnerability is network-exploitable without authentication and has complete impact on confidentiality, integrity, and availability.
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.78CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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.
-
Check if CX-Programmer is installedOpen Windows Control Panel > Programs and Features, or use PowerShell: Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName | Where-Object {$_.DisplayName -like '*CX-Programmer*'}Affected if CX-Programmer appears in the installed programs list
-
Locate CX-Programmer executable versionFind the CX-Programmer installation directory (typically C:\Program Files\OMRON\CX-Programmer\ or C:\Program Files (x86)\OMRON\CX-Programmer\), right-click on CX-Programmer.exe, select Properties, and view the Details tab for the Product VersionAffected if The executable is found and has a version number
-
Extract the exact version numberIn the Properties Details tab, record the Product Version number shown (for example, it may display as 9.7, 9.78, or a full build number)Affected if A version number is displayed in the file properties
-
Compare version to CVE thresholdCompare the installed version to 9.78 - if the version is 9.78 or lower (such as 9.7, 9.6, 9.5, etc.), the installed version falls within the vulnerable rangeAffected if Version number is 9.78 or lower, indicating the installed version is within the affected range <= 9.78
If CX-Programmer version 9.78 or lower is installed, the environment is affected by CVE-2022-3396 and is vulnerable to remote code execution.
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 dataUpdate CX-Programmer to a version beyond 9.78 once a patched release is available from OMRON. If patching is immediately impractical, network segment the affected systems, restrict access to authorized PLC engineering workstations only, and avoid opening untrusted CX-Programmer project files.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3396 — 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-2022-3396 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