Authentication beyond assertion expiry via missing SAML validation
Published Jun 19, 2020 · Updated Aug 5, 2024
Improper SAML response validation in Mattermost Server before 4.7.0, 4.6.2, and 4.5.2 allows remote authenticated users to reuse expired responses. The SAML sign-in path accepts a response after its embedded expiration date instead of rejecting the stale authentication assertion. Exposure requires SAML authentication and possession of a previously valid response, extending account access beyond the identity provider's intended lifetime.
Summary
What happened
Improper SAML response validation in Mattermost Server before 4.7.0, 4.6.2, and 4.5.2 allows remote authenticated users to reuse expired responses. The SAML sign-in path accepts a response after its embedded expiration date instead of rejecting the stale authentication assertion. Exposure requires SAML authentication and possession of a previously valid response, extending account access beyond the identity provider's intended lifetime.
The record
- CVE
- CVE-2018-21264
- Published
- Jun 19, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-20, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 19, 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.
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