ApostropheCMS session takeover via session migration tokens
apostrophecms apostrophe · @apostrophecms passport-bridge
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| apostrophe npm |
|
|
| @apostrophecms/passport-bridge npm |
|
|
apostrophecms apostrophe · @apostrophecms passport-bridge
| Product | Affected | Fixed in |
|---|---|---|
| apostrophe npm |
|
|
| @apostrophecms/passport-bridge npm |
|
|
ApostropheCMS is an open-source Node.js content management system. Prior to 4.33.0 of ApostropheCMS and 1.6.1 of passport-bridge, cross-host or cross-locale session migration places a single-use bearer session token in a redirect URL. A client that obtains and redeems a still-valid, unconsumed token before its first use can adopt the associated session, including through the passport-bridge cross-locale flow. This issue is fixed in ApostropheCMS 4.33.0 and passport-bridge 1.6.1.
From the CVE record · GitHub_M
Cross-host or cross-locale session migration places a single-use bearer session token in a redirect URL. A client that obtains and redeems a still-valid, unconsumed token before its first use can adopt the associated session, including through the passport-bridge cross-locale flow.
Check installations running npm apostrophe before 4.33.0 or @apostrophecms/passport-bridge before 1.6.1.