CVE-2024-22088: lotos · Use After Free
Affects lotosSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 53% 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 5 Jan 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubchendotjs/lotospkg:github/chendotjs/lotosOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2024-22088, organizations should immediately assess their exposure to Lotos WebServer versions up to 0.1.1. Since no official patches are currently available, the following specific actions are recommended: 1) Temporarily disable or restrict access to Lotos WebServer instances, especially those exposed to untrusted networks. 2) Implement network-level protections such as Web Application Firewalls (WAFs) or Intrusion Prevention Systems (IPS) configured to detect and block unusually long URI requests or suspicious traffic patterns targeting buffer handling. 3) Employ strict input validation and length restrictions on URI requests at the network edge or reverse proxy to prevent exploitation attempts. 4) Monitor server logs and network traffic for anomalous requests that could indicate exploitation attempts. 5) Consider migrating to alternative, actively maintained web server software until a patch is released. 6) Stay updated with vendor announcements and apply security patches immediately once available. 7) Conduct regular security audits and penetration testing focused on memory corruption vulnerabilities. These targeted mitigations go beyond generic advice by focusing on network-level controls and operational adjustments to reduce attack surface in the absence of a patch.
Description
Lotos WebServer through 0.1.1 (commit 3eb36cc) has a use-after-free in buffer_avail() at buffer.h via a long URI, because realloc is mishandled.