Policy bypass via trusted ingress attribute header
Published Feb 14, 2020 · Updated Aug 4, 2024
Improper input validation in Istio 1.3 through 1.3.6 allows remote attackers to bypass certain Mixer policies via a crafted header. The ingress proxy trusts an attacker-supplied x-istio-attributes value and uses its encoded source.uid when Mixer evaluates source-based policy. Exposure requires Mixer Policy to be enabled and selectively applied to a source equal to ingress; the feature is disabled by default.
Summary
What happened
Improper input validation in Istio 1.3 through 1.3.6 allows remote attackers to bypass certain Mixer policies via a crafted header. The ingress proxy trusts an attacker-supplied x-istio-attributes value and uses its encoded source.uid when Mixer evaluates source-based policy. Exposure requires Mixer Policy to be enabled and selectively applied to a source equal to ingress; the feature is disabled by default.
The record
- CVE
- CVE-2020-8843
- Published
- Feb 14, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-20, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 14, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo