Account access persistence via unrevoked session tokens
Published May 3, 2022 · Updated Sep 16, 2024
Insufficient session expiration in Shopizer 2.3.0 through 3.0.1 allows remote authenticated users to retain access after a password change. Password-change paths update the stored customer password, but existing JSON Web Tokens remain accepted by protected API endpoints instead of being invalidated. A previously issued customer session token is required, allowing continued use of that account after the user or an administrator changes its password.
Summary
What happened
Insufficient session expiration in Shopizer 2.3.0 through 3.0.1 allows remote authenticated users to retain access after a password change. Password-change paths update the stored customer password, but existing JSON Web Tokens remain accepted by protected API endpoints instead of being invalidated. A previously issued customer session token is required, allowing continued use of that account after the user or an administrator changes its password.
The record
- CVE
- CVE-2022-23063
- Published
- May 3, 2022
- Updated
- Sep 16, 2024
- Vendor
- Shopizer
- Product
- Shopizer
- Classifications
- CWE-613, T1550.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 3, 2022CVE publishedPublication date reported by the CVE source.
- Sep 16, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.3.0 <unspecified
- Affected versionversion=unspecified <=3.0.1
What conditions does exploitation require?
What is affected?
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