Skip to main content
VulnerabilityPublished Updated

CVE-2024-22824: Timo · Unrestricted File Upload

Affects TimoSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.0% chance of exploitation in 30 days – higher than 64% 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 20 Feb 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
GitHubauntvt/Timopkg:github/auntvt/TimoOther threatsAffected
  • =2.0.3
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-22824, organizations should immediately implement the following specific measures: 1) Restrict file uploads by enforcing strict server-side validation of file types, using allowlists rather than blocklists, and verifying file content signatures beyond file extensions. 2) Employ sandboxing or containerization for file upload handling to isolate potentially malicious files from critical system components. 3) Monitor and log all file upload activities, setting up alerts for anomalous or suspicious uploads. 4) Apply web application firewalls (WAFs) with custom rules to detect and block malicious upload attempts targeting the UploadController endpoint. 5) If a patch becomes available, prioritize its deployment after testing in a controlled environment. 6) Conduct regular security assessments and code reviews focusing on file upload mechanisms. 7) Limit permissions of the application process to minimize the impact of potential code execution. 8) Educate development teams on secure coding practices related to file uploads to prevent similar vulnerabilities in future releases.

Description

An issue in Timo v.2.0.3 allows a remote attacker to execute arbitrary code via the filetype restrictions in the UploadController.java component.

References

Community reviews

Loading reviews…