CVE-2024-12083
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 · uneditedPath Traversal Vulnerabilities (CWE-22) exist in NJ/NX-series Machine Automation Controllers. An attacker may use these vulnerabilities to perform unauthorized access and to execute unauthorized code remotely to the controller products.
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 confidencePath traversal vulnerabilities (CWE-22) in Omron NJ/NX-series Machine Automation Controllers allow attackers to manipulate file path inputs using '..' sequences to access unauthorized directories and files. Successful exploitation enables unauthorized access to the controller filesystem and can lead to remote code execution, posing significant risk to industrial operations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Network
- Complexity
- High
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:H/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.
-
Identify Omron NJ/NX controller in environmentLocate and document all Omron NJ-series or NX-series Machine Automation Controllers on the network by reviewing asset inventories, PLC program files, or network scans for Omron device signaturesAffected if No Omron NJ/NX controllers are present in the environment
-
Determine controller firmware versionAccess the controller via Omron Sysmac Studio software or the controller's web interface and retrieve the firmware version from the device information or system settings menuAffected if Firmware version cannot be determined or is older than current vendor-released versions (compare against Omron's official firmware release notes for CVE-2024-12083)
-
Verify if file transfer or web services are enabledCheck controller configuration in Sysmac Studio under Controller Settings > FTP Server or Web Server settings; determine if these services are enabled and accessibleAffected if FTP server, HTTP file operations, or file transfer features are enabled on the controller
-
Inspect network exposure of management interfacesReview firewall rules, network segmentation, and access control lists to determine if the controller's web management interface or FTP ports are exposed to untrusted networks or the internetAffected if Controller management interfaces (HTTP/HTTPS/FTP) are accessible from untrusted network segments or directly from the internet
-
Review logs for path traversal attemptsExamine controller event logs, syslog exports, or network intrusion detection alerts for patterns containing '..' sequences in file path requests, particularly on FTP or HTTP endpointsAffected if Logs contain file path requests with '..' sequences or evidence of directory traversal probing
A defender is affected if they have an Omron NJ/NX-series controller with file transfer or web services enabled, and the controller firmware has not been patched to address CVE-2024-12083.
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 dataApply vendor-supplied patches or firmware updates for NJ/NX-series controllers; restrict network access to controller management interfaces and implement strict input validation on all file path parameters.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-12083 — 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-2024-12083 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