Policy bypass via ignored negation predicates
Published Feb 14, 2020 · Updated Aug 5, 2024
Improper policy parsing in HashiCorp Sentinel 0.10.1 and earlier allows remote attackers to bypass intended policy decisions. The parser state machine ignores the not predicate when not contains, not in, or not matches follows an else or arithmetic expression, reversing the intended result. Exploitation requires an affected integration to enforce a specifically constructed policy expression, and the resulting security impact depends on the protected system.
Summary
What happened
Improper policy parsing in HashiCorp Sentinel 0.10.1 and earlier allows remote attackers to bypass intended policy decisions. The parser state machine ignores the not predicate when not contains, not in, or not matches follows an else or arithmetic expression, reversing the intended result. Exploitation requires an affected integration to enforce a specifically constructed policy expression, and the resulting security impact depends on the protected system.
The record
- CVE
- CVE-2019-19879
- Published
- Feb 14, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 14, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
- HashiCorp double-negation policy expression exampleproof of concept · demonstrated
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