Session Token Remains Valid After Logout in Multi-Worker Deployments
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Ericsson | CodeChecker | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Ericsson | Codechecker |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.139% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Ericsson
Ericsson codechecker |
|
| Vendors & Products |
Ericsson
Ericsson codechecker |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | CodeChecker's web server fails to fully invalidate a session token on logout when the server runs with more than one API worker process (the default). Each worker process maintains its own in-memory session cache; logout only clears the cache of the single worker that handles the request (plus the shared database record). Other workers continue to honor the destroyed token from their stale in-memory copies until the session's lifetime expires. An attacker who has captured a valid token can therefore keep impersonating the user after the user has logged out. | |
| Title | Session Token Remains Valid After Logout in Multi-Worker Deployments | |
| Weaknesses | CWE-613 | |
| References |
| |
| Metrics |
cvssV4_0
|