NVD / CVE Program· CNA jpcert

CVE-2024-27121: Path traversal vulnerability exists in Machine Automation Controller NJ Series and Machine Automation Controller NX Series.

Noroxi assessment

Priority: Monitor (action score 28/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.88% (FIRST EPSS); higher than 59.2% of all records.
Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
According to the record, no fixed version is available yet.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Path 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.

HighCVSS 7.2 · v3.1—No exploit No fix recorded

Published: Mar 12, 2024
Updated: Jun 17, 2026
EPSS: 0.8% · 59th percentile
CWE: CWE-22

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 28 / 40 · 7.2 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.8%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
omron	nj101-1000 firmware	cpe:2.3:o:omron:nj101-1000_firmware
omron	nj101-1020 firmware	cpe:2.3:o:omron:nj101-1020_firmware
omron	nj101-9000 firmware	cpe:2.3:o:omron:nj101-9000_firmware
omron	nj101-9020 firmware	cpe:2.3:o:omron:nj101-9020_firmware
omron	nj301-1100 firmware	cpe:2.3:o:omron:nj301-1100_firmware
omron	nj301-1200 firmware	cpe:2.3:o:omron:nj301-1200_firmware
omron	nj501-1300 firmware	cpe:2.3:o:omron:nj501-1300_firmware
omron	nj501-1320 firmware	cpe:2.3:o:omron:nj501-1320_firmware
omron	nj501-1340 firmware	cpe:2.3:o:omron:nj501-1340_firmware
omron	nj501-1400 firmware	cpe:2.3:o:omron:nj501-1400_firmware
omron	nj501-1420 firmware	cpe:2.3:o:omron:nj501-1420_firmware
omron	nj501-1500 firmware	cpe:2.3:o:omron:nj501-1500_firmware

and 13 more

Versions reported by the vendor

Affected version ranges reported by the assigning authority (jpcert). Independent of NVD's CPE analysis and usually ahead of it.

OMRON Corporation Machine Automation Controller NJ Series
- NJ101-[][][][] Ver.1.64.03 and earlier, NJ301-[][][][] Ver.1.64.00 and earlier, NJ501-1[]0[] Ver.1.64.03 and earlier, NJ501-1[]2[] Ver.1.64.00 and earlier, NJ501-1340 Ver.1.64.00 and earlier, NJ501-4[][][] Ver.1.64.00 and earlier, NJ501-5300 Ver.1.64.00 and earlier, NJ501-R[][][] Ver.1.64.00 and earlieraffected
OMRON Corporation Machine Automation Controller NX Series
- NX1P2-[][][][][][] Ver.1.64.00 and earlier, NX1P2-[][][][][][]1 Ver.1.64.00 and earlier, NX102-[][][][] Ver.1.64.00 and earlier, NX502-[][][][] Ver.1.65.01 and earlier, NX701-[][][][] Ver.1.35.00 and earlier, NX-EIP201 Ver.1.00.01 and earlieraffected

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-24-0195 · Mar 12, 2024(OMRON Güvenlik Güncellemesi)

All national notices →

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
Administrator privileges are required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: High
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

The bug in code

The whole CWE-22 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const file = path.join(ROOT, req.query.name);
2res.sendFile(file);

Fixed

1const file = path.resolve(ROOT, req.query.name);
2if (!file.startsWith(ROOT + path.sep)) {
3  return res.sendStatus(400);
4}
5res.sendFile(file);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

jvn.jp/en/vu/JVNVU95852116/index.html

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records