Hydro: Insufficient session expiration when recreating sessions
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| hydro-dev | Hydro | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Hydro-dev | Hydro |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-94jp-7776-qj6q | Hydro: Insufficient session expiration when recreating sessions |
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.473% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Hydro-dev
Hydro-dev hydro |
|
| Vendors & Products |
Hydro-dev
Hydro-dev hydro |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Hydro is a next-generation high-performance online judge platform. From 4.10.4 until 5.0.2, the session recreation logic in packages/hydrooj/src/service/layers/base.ts creates a replacement session token without deleting the previous token from the server-side session token store, so an old sid cookie can remain valid after logout or another renewal flow. An attacker who possesses a victim's previously valid stale cookie can replay it over HTTP or HTTPS without knowing the victim's username or password and without victim interaction at exploitation time. Successful replay can take over the victim's account, disclose private data, and permit unauthorized modification or deletion of data available to that account. This issue is fixed in version 5.0.2. | |
| Title | Hydro: Insufficient session expiration when recreating sessions | |
| Weaknesses | CWE-613 | |
| References |
| |
| Metrics |
cvssV4_0
|