Policy duplication via missing backend authorization check
Published Jul 13, 2021 · Updated Aug 3, 2024
Authorization bypass in Stormshield SES Evolution before 2.1.0 allows context-dependent attackers to duplicate security policies. The backend accepts a policy-duplication operation in a read-only user's security-policy context without enforcing the required write authorization. Exploitation requires that user to execute a malicious program; the resulting integrity impact is limited to creation of a duplicate policy.
Summary
What happened
Authorization bypass in Stormshield SES Evolution before 2.1.0 allows context-dependent attackers to duplicate security policies. The backend accepts a policy-duplication operation in a read-only user's security-policy context without enforcing the required write authorization. Exploitation requires that user to execute a malicious program; the resulting integrity impact is limited to creation of a duplicate policy.
The record
- CVE
- CVE-2021-31224
- Published
- Jul 13, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1203
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 13, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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
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