Skip to main content
VulnerabilityPublished Updated

CVE-2024-55544: ORing IAP-420 · Command Injection

Affects ORing IAP-420Source CVE Database V5

0

Not known to be exploited · 12% EPSS · CVSS 8.7 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
12.3% chance of exploitation in 30 days – higher than 96% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Dec 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
ORing IAP-420Affected
  • =0
Fixed in–

AI-suggested

  1. Immediately inventory all ORing IAP-420 devices in your environment and identify those running version 2.01e or below.
  2. Restrict network access to the device management interface using firewalls and network segmentation, limiting access to trusted administrators only.
  3. Implement strong authentication and monitoring on management interfaces to detect unusual login attempts or command executions.
  4. Monitor network traffic for anomalous commands or patterns indicative of exploitation attempts.
  5. Engage with ORing or authorized vendors to obtain firmware updates or patches as soon as they become available.
  6. Until patches are released, consider isolating vulnerable devices from critical networks or deploying virtual patching via intrusion prevention systems (IPS) that can detect and block command injection attempts.
  7. Conduct regular security assessments and penetration tests focusing on industrial control systems to identify similar vulnerabilities.
  8. Train staff on the risks of command injection and the importance of secure device management practices.

Description

Missing input validation in the ORing IAP-420 web-interface allows authenticated Command Injections on OS level.This issue affects IAP-420 version 2.01e and below.

References

Community reviews

Loading reviews…