CVE-2024-38462: irods · Untrusted Search Path
Affects irodsSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 4.3.2 as a priority.
Data as of 26 Oct 2026, 11:42 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.3.2
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 16 Jun 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
Upgrade irods/irods to 4.3.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubirods/irodspkg:github/irods/irodsOther 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-38462, organizations should immediately upgrade iRODS to version 4.3.2 or later where the vulnerability is addressed. Until patching is possible, restrict the execution environment of the mail binary by enforcing strict path controls and permissions to prevent unauthorized replacement or manipulation. Implement application whitelisting to ensure only trusted binaries are executed. Monitor system and application logs for unusual activity related to mail sending functions. Network segmentation and firewall rules should limit exposure of iRODS servers to untrusted networks. Conduct regular audits of the environment to detect any unauthorized changes to binaries or environment variables influencing the mail binary path. Educate administrators about the risks of unsafe external dependencies and encourage secure coding practices for custom extensions or scripts interacting with iRODS. Finally, maintain up-to-date backups and incident response plans to quickly recover from potential exploitation.
Description
iRODS before 4.3.2 provides an msiSendMail function with a problematic dependency on the mail binary, such as in the mailMS.cpp#L94-L106 reference.