CVE-2024-45166: UCI IDOL · Uncontrolled Resource Consumption
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 1.0% chance of exploitation in 30 days – higher than 63% 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:HExploitation evidence
Disclosed: evidence found.
CVE published 22 Aug 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 an official patch is released, organizations should implement network-level controls such as firewall rules to restrict access to UCI IDOL 2 services only to trusted internal networks and known IP addresses. Employ intrusion detection and prevention systems (IDS/IPS) with signatures or anomaly detection tuned to identify unusual login attempts or memory corruption patterns related to this vulnerability. Conduct thorough logging and monitoring of login attempts to detect the characteristic pattern of five logins triggering the EIP overwrite. Consider deploying application-layer gateways or reverse proxies to add an additional security layer and filter malformed inputs. Engage with the vendor for timely updates and apply patches immediately upon release. Additionally, perform regular backups and have incident response plans ready to mitigate potential exploitation consequences. Where feasible, isolate vulnerable systems from the internet and untrusted networks to reduce exposure.
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. There is an access violation and EIP overwrite after five logins.
References
- syss.de/en/responsible-disclosure-policy (opens in a new tab)
- uci.de/products/index.html (opens in a new tab)
- uci.de/download/idol2-client.html (opens in a new tab)
- download.uci.de/idol2/idol2Client_2_12.exe (opens in a new tab)
- syss.de/fileadmin/dokumente/Publikationen/Advisories/SYSS-2024-050.txt (opens in a new tab)