Account reentry via persistent browser credentials
Published Dec 25, 2022 · Updated Apr 15, 2025
Session fixation in Simmeth Lieferantenmanager before 5.6 allows attackers to regain access to a logged-out user's account. Logout changes only the frontend state, leaving the username and encrypted password valid in browser local storage; opening /LMS/LM/#main restores the authenticated state. Exploitation requires control of the browser context holding the victim's stored credentials and grants that account's application access.
Summary
What happened
Session fixation in Simmeth Lieferantenmanager before 5.6 allows attackers to regain access to a logged-out user's account. Logout changes only the frontend state, leaving the username and encrypted password valid in browser local storage; opening /LMS/LM/#main restores the authenticated state. Exploitation requires control of the browser context holding the victim's stored credentials and grants that account's application access.
The record
- CVE
- CVE-2022-44017
- Published
- Dec 25, 2022
- Updated
- Apr 15, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-384, T1078
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 25, 2022CVE publishedPublication date reported by the CVE source.
- Apr 15, 2025Record 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
- SEC Consult session-management proof of conceptproof 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