Continued account access via persistent sessions
Published Mar 15, 2021 · Updated Aug 4, 2024
Insufficient session expiration in DomainMOD 4.15.0 allows remote attackers to retain account access through old browser sessions. The password-change path updates the credential but does not invalidate sessions already established in the same or another browser or device. Remote attackers must possess a valid pre-change session token, which continues to authorize the account after its password changes.
Summary
What happened
Insufficient session expiration in DomainMOD 4.15.0 allows remote attackers to retain account access through old browser sessions. The password-change path updates the credential but does not invalidate sessions already established in the same or another browser or device. Remote attackers must possess a valid pre-change session token, which continues to authorize the account after its password changes.
The record
- CVE
- CVE-2020-35358
- Published
- Mar 15, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-613, T1550.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 15, 2021CVE 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.
Weakness, pattern, technique
Public exploit references
- DomainMOD session-persistence demonstrationproof of concept · unverified
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