CVE-2024-24565 is a medium-severity (CVSS 5.7) Path Traversal vulnerability in io.crate:crate. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2024-24565 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
CrateDB database has an arbitrary file read vulnerability
Real-World Exposure
io.crate:crate☕io.crate:crate☕io.crate:crate☕io.crate:crateReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
CrateDB is a distributed SQL database that makes it simple to store and analyze massive amounts of data in real-time. There is a COPY FROM function in the CrateDB database that is used to import file data into database tables. This function has a flaw, and authenticated attackers can use the COPY FROM function to import arbitrary file content into database tables, resulting in information leakage. This vulnerability is patched in 5.3.9, 5.4.8, 5.5.4, and 5.6.1.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.crate:crate | all versions | 5.3.9 |
| ☕Maven | io.crate:crate | ≥ 5.4.0&&< 5.4.8 | 5.4.8 |
| ☕Maven | io.crate:crate | ≥ 5.5.0&&< 5.5.4 | 5.5.4 |
| ☕Maven | io.crate:crate | ≥ 5.6.0&&< 5.6.1 | 5.6.1 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.crate:crate. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update io.crate:crate to 5.3.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-24565 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2024-24565 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2024-24565. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2024-24565 in your dependencies?
O3 detects CVE-2024-24565 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.