The undertow client is not checking the server identity presented by the server certificate in https connections. This is a compulsory step (at least it should be performed by default) in https and in http/2. I would add it to any TLS client protocol.
AI analysis not yet available
Plain-English explanation, risk summary, and remediation steps will appear here once AI analysis is complete.
No Fix Known
No patch has been released yet. Apply workarounds or mitigations where available.
| Vendor | Product | Versions | Fixed In |
|---|---|---|---|
| redhat | build_of_quarkus | - | - |
| redhat | integration_camel_for_spring_boot | - | - |
| redhat | integration_camel_k |
Published
CVE disclosed publicly
Last Modified
Most recent update
Indexed to CVEInsight
Added to this platform
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
10
Affected Products
6
References
redhat / build_of_quarkus
| - |
| - |
| redhat | integration_service_registry | - | - |
| redhat | jboss_enterprise_application_platform | - | - |
| redhat | jboss_fuse | - | - |
| redhat | migration_toolkit_for_applications | - | - |
| redhat | migration_toolkit_for_runtimes | - | - |
| redhat | single_sign-on | - | - |
| redhat | undertow | - | - |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Exploitability
Impact