CVE-2017-12158 — It was found that Keycloak would accept a HOST header URL in the admin console and use it to determine web resource locations

Matched remediation archetype

HTTP request smuggling and message-boundary ambiguity

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

• Inventory every proxy, CDN, gateway, load balancer, service mesh, and application server hop on affected request paths.
• Compare documented parsing and normalization behavior for message length, transfer coding, duplicate headers, and protocol translation.
• Identify connection reuse and which downstream services trust headers added by intermediaries.

Remediate safely

• Update affected intermediaries and origin servers and align them on a single standards-compliant request framing policy.
• Reject ambiguous length, transfer-coding, duplicate, malformed, and unsupported framing before forwarding.
• Normalize or remove hop-by-hop and identity headers at one controlled boundary and add multi-hop regression tests.