Vendor
Heimdall IP Spoofing via Unvalidated Forwarding Headers
2 rules 2 TTPsA high-severity vulnerability in dadrus/heimdall (versions <= 0.17.16) enables attackers to spoof client IP addresses by injecting unvalidated or malformed values into `Forwarded` or `X-Forwarded-For` HTTP headers, potentially bypassing access controls or propagating malicious IP data to upstream services when `trusted_proxies` is configured.
Heimdall Proxy Forwarded Header Injection via Unsanitized Host Header
1 rule 1 TTPAttackers can exploit Heimdall proxy versions <= 0.17.16 operating in proxy mode by injecting malicious values into the `Host` HTTP header, leading to the construction of a manipulated `Forwarded` header that can spoof client IP addresses for upstream services, potentially bypassing IP-based access controls.
Heimdall Authorization Bypass via Case-Sensitive URL-Encoded Slash Handling
2 rules 1 TTPHeimdall versions before 0.17.14 are vulnerable to inconsistent path interpretation due to case-sensitive handling of URL-encoded slashes; when `allow_encoded_slashes` is set to `off` (the default), the lowercase `%2f` is not recognized, potentially leading to authorization bypass if the default rule is overly permissive and the upstream service interprets `%2f` as a path separator.
Heimdall Host Matching Case-Sensitivity Vulnerability
2 rules 1 TTPHeimdall performs case-sensitive host matching, which can lead to policy bypass because HTTP hostnames are case-insensitive, potentially leading to unauthorized access, data modification, or privilege escalation if the request host is part of the rule.
Heimdall Authorization Bypass via Path Normalization Mismatch
2 rules 2 TTPsHeimdall is vulnerable to an authorization bypass due to a path normalization mismatch between Heimdall and downstream components, potentially leading to unauthorized access and privilege escalation.