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 |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: mitre
Published: 2020-02-14T18:45:19
Updated: 2020-02-14T18:45:19
Reserved: 2020-02-10T00:00:00
Link: CVE-2020-8843
JSON object: View
NVD Information
Status : Analyzed
Published: 2020-02-14T19:15:10.683
Modified: 2020-02-19T16:16:00.003
Link: CVE-2020-8843
JSON object: View
Redhat Information
No data.
CWE