Type confusion in FalkorDB GRAPH.QUERY via the --bolt argument
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| FalkorDB | FalkorDB | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Falkordb | Falkordb |
|
Vendor Solution
Upgrade FalkorDB to version 4.20.0 or later. Bolt protocol support, including the code affected by this issue, was removed in 4.20.0.
Vendor Workaround
Use Redis ACLs to restrict the GRAPH.QUERY command to trusted users, and do not expose the instance to untrusted networks.
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.354% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A type confusion vulnerability in the _read_flags function (src/commands/cmd_dispatcher.c) in FalkorDB before 4.20.0 allows a remote authenticated attacker who can run GRAPH.QUERY to cause a denial of service and possibly disclose or corrupt memory. The function accepts a --bolt argument from any client and casts the following command argument, a Redis string object, to a Bolt client structure without checking its origin; the result-set code then dereferences pointers read from that object. The argument is parsed even when the Bolt endpoint is disabled, so default configurations are affected. | |
| Title | Type confusion in FalkorDB GRAPH.QUERY via the --bolt argument | |
| First Time appeared |
Falkordb
Falkordb falkordb |
|
| Weaknesses | CWE-843 | |
| CPEs | cpe:2.3:a:falkordb:falkordb:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Falkordb
Falkordb falkordb |
|
| References |
| |
| Metrics |
cvssV3_1
|