Skip to main content
VulnerabilityPublished

CVE-2024-45167: UCI IDOL · Improper Input Validation

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.2% chance of exploitation in 30 days – higher than 68% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Aug 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

AI-suggested

Until official patches are released, organizations should implement network-level protections such as strict firewall rules to limit access to UCI IDOL 2 services only to trusted IP addresses. Deploy intrusion detection and prevention systems (IDS/IPS) with signatures or heuristics to detect anomalous XmlMessage traffic patterns. Conduct thorough input validation and sanitization on any interfaces interacting with IDOL2 if possible. Monitor CPU usage and system logs for unusual spikes or behavior indicative of exploitation attempts. Segment networks to isolate critical IDOL2 deployments from broader enterprise networks to contain potential compromises. Engage with the vendor for timely updates and apply patches immediately upon availability. Consider temporary disabling or restricting vulnerable features if feasible. Perform regular security assessments and penetration testing focused on deserialization and input validation weaknesses.

Description

An issue was discovered in UCI IDOL 2 (aka uciIDOL or IDOL2) through 2.12. Due to improper input validation, improper deserialization, and improper restriction of operations within the bounds of a memory buffer, IDOL2 is vulnerable to Denial-of-Service (DoS) attacks and possibly remote code execution. A certain XmlMessage document causes 100% CPU consumption.

References

Community reviews

Loading reviews…