Protected-data access via logged-out token replay
Published Aug 16, 2021 · Updated Aug 4, 2024
Incorrect access control in TaleLin Lin-CMS-Flask 0.1.1 allows remote attackers to access protected data by replaying a logged-out token. The logout session handling leaves the authentication token valid, and protected API endpoints continue accepting it after logout. Exploitation requires possession of a previously issued token and grants the authorization associated with that token, including access to the user list.
Summary
What happened
Incorrect access control in TaleLin Lin-CMS-Flask 0.1.1 allows remote attackers to access protected data by replaying a logged-out token. The logout session handling leaves the authentication token valid, and protected API endpoints continue accepting it after logout. Exploitation requires possession of a previously issued token and grants the authorization associated with that token, including access to the user list.
The record
- CVE
- CVE-2020-18701
- Published
- Aug 16, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-613, CWE-863, T1078
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 16, 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
- Logged-out token replay procedureproof 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