An issue was discovered in Istio 1.3 through 1.3.6. Under certain circumstances, it is possible to bypass a specifically configured Mixer policy. Istio-proxy accepts the x-istio-attributes header at ingress that can be used to affect policy decisions when Mixer policy selectively applies to a source equal to ingress. To exploit this vulnerability, someone has to encode a source.uid in this header. This feature is disabled by default in Istio 1.3 and 1.4.
References
Link | Resource |
---|---|
https://github.com/istio/istio/commits/master | Patch |
https://istio.io/news/security/ | Vendor Advisory |
https://istio.io/news/security/istio-security-2020-002/ | Vendor Advisory |
https://github.com/istio/istio/commits/master | Patch |
https://istio.io/news/security/ | Vendor Advisory |
https://istio.io/news/security/istio-security-2020-002/ | Vendor Advisory |
Configurations
History
21 Nov 2024, 05:39
Type | Values Removed | Values Added |
---|---|---|
References | () https://github.com/istio/istio/commits/master - Patch | |
References | () https://istio.io/news/security/ - Vendor Advisory | |
References | () https://istio.io/news/security/istio-security-2020-002/ - Vendor Advisory |
Information
Published : 2020-02-14 19:15
Updated : 2024-11-21 05:39
NVD link : CVE-2020-8843
Mitre link : CVE-2020-8843
CVE.ORG link : CVE-2020-8843
JSON object : View
Products Affected
istio
- istio
CWE
CWE-20
Improper Input Validation