[GEODE-10623] Remediation of CVE-2026-64607 - #8050
Merged
Merged
Conversation
marinov-code
approved these changes
Sep 3, 2026
HttpClient 5.5 changed the hostname verification default on the DefaultClientTlsStrategy(SSLContext, HostnameVerifier) constructor. It previously passed HostnameVerificationPolicy.CLIENT, letting the supplied verifier alone decide whether a certificate matches the endpoint. It now passes no policy, which AbstractClientTlsStrategy resolves to BOTH when a verifier is present, so JSSE endpoint identification runs in addition to the supplied verifier rather than being replaced by it. Pass HostnameVerificationPolicy.CLIENT explicitly when the caller provides a verifier, restoring the documented behavior of ClusterManagementServiceBuilder.setHostnameVerifier. When no verifier is supplied, use the single-argument constructor rather than CLIENT with a null verifier: 5.5 also dropped the substitution of HttpsSupport.getDefaultHostnameVerifier() for a null verifier, so CLIENT with null would skip endpoint checking entirely. The single-argument form keeps the library's own endpoint identification. This surfaced in ClientClusterManagementSSLTest, whose certificate carries CN=localhost with no subjectAltName. The reported symptom was misleading: DefaultHttpClientConnectionOperator performs the TLS upgrade inside its per-address retry loop, so the handshake failure on 127.0.0.1 was treated as a reason to try the next address. localhost also resolves to ::1, where nothing is listening, and that trailing connection refusal was what got reported.
JinwooHwang
added a commit
to JinwooHwang/geode
that referenced
this pull request
Sep 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Remediation of CVE-2026-64607
For all changes, please confirm:
develop)?gradlew buildrun cleanly?