After user deletion in MongoDB Server the improper invalidation of authorization sessions allows an authenticated users session to persist and become conflated with new accounts, if those accounts reuse the names of deleted ones. This issue affects MongoDB Server v4.0 versions prior to 4.0.9; MongoDB Server v3.6 versions prior to 3.6.13 and MongoDB Server v3.4 versions prior to 3.4.22.
Workaround: After deleting one or more users, restart any nodes which may have had active user authorization sessions.
Refrain from creating user accounts with the same name as previously deleted accounts.
According to WASC, “Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization.”
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Mongodb | Mongodb | 3.4.0 (including) | 3.4.22 (excluding) |
| Mongodb | Mongodb | 3.6.0 (including) | 3.6.13 (excluding) |
| Mongodb | Mongodb | 4.0.0 (including) | 4.0.9 (excluding) |
| Mongodb | Ubuntu | bionic | * |
| Mongodb | Ubuntu | disco | * |
| Mongodb | Ubuntu | eoan | * |
| Mongodb | Ubuntu | esm-apps/xenial | * |
| Mongodb | Ubuntu | esm-infra-legacy/trusty | * |
| Mongodb | Ubuntu | focal | * |
| Mongodb | Ubuntu | trusty | * |
| Mongodb | Ubuntu | trusty/esm | * |
| Mongodb | Ubuntu | xenial | * |