CVE-2023-45860

Hazelcast Platform permission checking in CSV File Source connector

Workaround

Disabling Hazelcast Jet processing engine in Hazelcast member configuration workarounds the issue. As a result SQL and Jet jobs won't work.

In Hazelcast Platform through 5.3.4, a security issue exists within the SQL mapping for the CSV File Source connector. This issue arises from inadequate permission checking, which could enable unauthorized clients to access data from files stored on a member's filesystem.

Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.

CVE-2023-45860 has a CVSS score of 6.5 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (5.3.5, 5.2.5); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

Fix versions: 5.3.5, 5.4.0-BETA-1

1. What is CVE-2023-45860? CVE-2023-45860 is a high-severity SQL injection vulnerability in com.hazelcast:hazelcast (maven), affecting versions >= 5.3.0, <= 5.3.4. It is fixed in 5.3.5, 5.2.5. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
2. How severe is CVE-2023-45860? CVE-2023-45860 has a CVSS score of 6.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2023-45860?
   • com.hazelcast:hazelcast (maven) (versions >= 5.3.0, <= 5.3.4)
   • com.hazelcast:hazelcast-enterprise (maven) (versions >= 5.3.0, <= 5.3.4)
4. Is there a fix for CVE-2023-45860? Yes. CVE-2023-45860 is fixed in 5.3.5, 5.2.5. Upgrade to this version or later.
5. Is CVE-2023-45860 exploitable, and should I be worried? Whether CVE-2023-45860 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2023-45860 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2023-45860?
   • Upgrade com.hazelcast:hazelcast to 5.3.5 or later
   • Upgrade com.hazelcast:hazelcast-enterprise to 5.3.5 or later
   • Upgrade com.hazelcast:hazelcast-enterprise to 5.2.5 or later
   • Upgrade com.hazelcast:hazelcast to 5.2.5 or later

Other vulnerabilities in com.hazelcast:hazelcast