Skip to content
Fencer Vulns
medium 5.7

CVE-2024-24565 json

CrateDB database has an arbitrary file read vulnerability

published 2024-01-30 2 y ago modified 2026-09-10 1 mo ago also GHSA-475g-vj6c-xf96 , EUVD-2024-0241

cvss
5.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
3.1%
EPSS 3.1% chance of exploitation in 30 days, percentile 87%
public exploits
0
none known, plus a Nuclei check

Summary

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.

Patch / fix

  • maven io.crate:crate 5.3.9, 5.4.8, 5.5.4, 5.6.1
  • cratedb cratedb 5.3.9, 5.4.8, 5.5.4, 5.6.1

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

3.08% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • Nuclei template CrateDB Database - Arbitrary File Read nuclei detection template
  • github.com https://github.com/crate/crate/security/advisories/GHSA-475g-vj6c-xf96 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 5.7 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
GitHub 3.1 5.7 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven io.crate:crate
<5.3.9
>=5.4.0, <5.4.8
>=5.5.0, <5.5.4
>=5.6.0, <5.6.1
5.3.9
5.4.8
5.5.4
5.6.1

Affected products

  • crate crate
  • cratedb cratedb

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.