CVE-2023-4586 in netty - is quarkus already dealing with this or is there a way to easily configure quarkus to be safe

[joergsesterhenn]

So there is this GHSA-57m8-f3v5-hm5m
By using quarkus we are using netty and we want to make sure that netty is configured in a safe way.

Can someone comment on whether quarkus configures netty to validate hostnames when using TLS or if there is some way to configure this through quarkus?

[joergsesterhenn]

Verification of hostnames is enabled per default in quarkus:
https://quarkus.io/guides/all-config#quarkus-rest-client-config_quarkus.rest-client.verify-host

I interpret this as: CVE-2023-4586 is no issue for quarkus in default configuration.