CVE-2024-27121
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 vulnerability exists in Machine Automation Controller NJ Series and Machine Automation Controller NX Series. An arbitrary file in the affected product may be accessed or arbitrary code may be executed by processing a specially crafted request sent from a remote attacker with an administrative privilege. As for the details of the affected product names/versions, see the information provided by the vendor under [References] section.
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 confidenceA path traversal vulnerability (CWE-22) in Omron Machine Automation Controllers NJ Series and NX Series allows authenticated remote attackers with administrative privileges to access arbitrary files or execute arbitrary code by sending specially crafted requests. The vulnerability is exploitable remotely, indicating improper input sanitization on file path parameters.
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
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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 the Omron controller modelLocate the controller nameplate or check system documentation for the model number. Confirm it is an NJ Series or NX Series Machine Automation Controller.Affected if The device is an Omron NJ Series or NX Series controller
-
Determine if web-based management is enabledCheck the controller configuration for enabled web servers, HTTP/HTTPS interfaces, or API endpoints used for remote administration.Affected if Web management or API interfaces are enabled and accessible over the network
-
Verify administrative account exposureReview user accounts configured on the controller and check if administrative accounts can be accessed remotely (not just via physical console).Affected if Administrative accounts exist and remote access is permitted
-
Identify file handling featuresExamine available controller functions for file upload, backup/restore, configuration import, or any feature that accepts file path parameters.Affected if The controller has file upload, backup, or configuration features accessible to administrative users
-
Inspect for directory traversal indicatorsReview system logs and access logs for patterns containing ../ sequences or unusual path requests that may indicate exploitation attempts.Affected if Logs show requests with traversal sequences or anomalous file path access attempts
You are affected if you operate an Omron NJ Series or NX Series controller with remote administrative access enabled and file path handling features exposed to authenticated administrators.
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-provided patches for affected NJ/NX Series versions. Implement strict input validation on all file path parameters, restrict administrative access following least-privilege principles, and monitor for anomalous requests containing directory traversal sequences (e.g., ../../../).
- 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-27121 — 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-27121 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