ghsa-7774-7vr3-cc8j
Vulnerability from github
Impact
According to RFC 4343, Istio authorization policy should compare the hostname in the HTTP Host header in a case insensitive way, but currently the comparison is case sensitive. The Envoy proxy will route the request hostname in a case-insensitive way which means the authorization policy could be bypassed.
As an example, the user may have an authorization policy that rejects request with hostname "httpbin.foo" for some source IPs, but the attacker can bypass this by sending the request with hostname "Httpbin.Foo".
Patches
- Istio 1.11.1 and above
- Istio 1.10.4 and above
- Istio 1.9.8 and above
Workarounds
A Lua filter may be written to normalize Host header before the authorization check. This is similar to the Path normalization presented in the Security Best Practices guide.
References
More details can be found in the Istio Security Bulletin.
For more information
If you have any questions or comments about this advisory, please email us at istio-security-vulnerability-reports@googlegroups.com
{ "affected": [ { "package": { "ecosystem": "Go", "name": "istio.io/istio" }, "ranges": [ { "events": [ { "introduced": "0" }, { "fixed": "1.9.8" } ], "type": "ECOSYSTEM" } ] }, { "package": { "ecosystem": "Go", "name": "istio.io/istio" }, "ranges": [ { "events": [ { "introduced": "1.10.0" }, { "fixed": "1.10.4" } ], "type": "ECOSYSTEM" } ] }, { "package": { "ecosystem": "Go", "name": "istio.io/istio" }, "ranges": [ { "events": [ { "introduced": "1.11.0" }, { "fixed": "1.11.1" } ], "type": "ECOSYSTEM" } ], "versions": [ "1.11.0" ] } ], "aliases": [ "CVE-2021-39155" ], "database_specific": { "cwe_ids": [ "CWE-178" ], "github_reviewed": true, "github_reviewed_at": "2021-08-25T22:29:16Z", "nvd_published_at": "2021-08-24T23:15:00Z", "severity": "HIGH" }, "details": "### Impact\nAccording to [RFC 4343](https://datatracker.ietf.org/doc/html/rfc4343), Istio authorization policy should compare the hostname in the HTTP Host header in a case insensitive way, but currently the comparison is case sensitive. The Envoy proxy will route the request hostname in a case-insensitive way which means the authorization policy could be bypassed.\n \nAs an example, the user may have an authorization policy that rejects request with hostname \"httpbin.foo\" for some source IPs, but the attacker can bypass this by sending the request with hostname \"Httpbin.Foo\".\n\n### Patches\n* Istio 1.11.1 and above\n* Istio 1.10.4 and above\n* Istio 1.9.8 and above\n\n### Workarounds\nA Lua filter may be written to normalize Host header before the authorization check. This is similar to the Path normalization presented in the [Security Best Practices](https://istio.io/latest/docs/ops/best-practices/security/#case-normalization) guide.\n\n### References\nMore details can be found in the [Istio Security Bulletin](https://istio.io/latest/news/security/istio-security-2021-008).\n\n### For more information\nIf you have any questions or comments about this advisory, please email us at istio-security-vulnerability-reports@googlegroups.com\n", "id": "GHSA-7774-7vr3-cc8j", "modified": "2021-12-13T13:09:54Z", "published": "2021-08-30T16:15:56Z", "references": [ { "type": "WEB", "url": "https://github.com/istio/istio/security/advisories/GHSA-7774-7vr3-cc8j" }, { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2021-39155" }, { "type": "WEB", "url": "https://github.com/istio/istio/commit/084b417a486dbe9b9024d4812877016a484572b1" }, { "type": "WEB", "url": "https://github.com/istio/istio/commit/76ed51413ddd2a7fa253a368ab20a9cec5fb1cbe" }, { "type": "WEB", "url": "https://github.com/istio/istio/commit/90b00bdf891e6c770cb3235c14a9b1fda96cc7c5" }, { "type": "WEB", "url": "https://datatracker.ietf.org/doc/html/rfc4343" }, { "type": "PACKAGE", "url": "https://github.com/istio/istio" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L", "type": "CVSS_V3" } ], "summary": "Authorization Policy Bypass Due to Case Insensitive Host Comparison" }
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.