There is an HTTP authentication bypass vulnerability in the CrateDB database about crate HOT 3 CLOSED

@Tu0Laj1
Thank you a lot for reporting. We have fixed this inside CrateDB with #15234.
We will release this fix asap for all current supported releases (5.2 -> 5.5).

On CrateDB Cloud, the team took already the necessary actions to mitigate it for all existing clusters, and is working on further improvements to avoid such security risks in the future.

from crate.

We have just released CrateDB 5.2.11, 5.3.8, 5.4.7 and 5.5.2 which contain the related fix.

from crate.

Thank you for bringing this issue to our attention. We are currently looking into it with urgency.

As a preliminary measure, it's advisable to restrict superuser access to the PostgreSQL protocol.

        - -Cauth.host_based.config.0.user=crate
        - -Cauth.host_based.config.0.address=_local_
        - -Cauth.host_based.config.0.method=trust
        - -Cauth.host_based.config.0.protocol=pg

Additionally, it is highly recommended for CrateDB Cloud Clusters to use the IP Allow-List feature, effectively blocking access at the TCP level.

Which can be found in the Cluster > Manage Tab

from crate.