CVE-2020-8843

Description

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.

Category

7.4
CVSS
Severity: High
CVSS 3.1 •
CVSS 2.0 •
EPSS 0.37%
Vendor Advisory istio.io Vendor Advisory istio.io
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
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

Frequently Asked Questions

What is the severity of CVE-2020-8843?
CVE-2020-8843 has been scored as a high severity vulnerability.
How to fix CVE-2020-8843?
To fix CVE-2020-8843, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2020-8843 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2020-8843 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.