The function mt_rand is used to generate session tokens, this function is cryptographically flawed due to its nature being one…
Mautic·CWE-327·Published 2021-08-30
The function mt_rand is used to generate session tokens, this function is cryptographically flawed due to its nature being one pseudorandomness, an attacker can take advantage of the cryptographically insecure nature of this function to enumerate session tokens for accounts that are not under his/her control This issue affects: Mautic Mautic versions prior to 3.3.4; versions prior to 4.0.0.
The function mt_rand is used to generate session tokens, this function is cryptographically flawed due to its nature being one pseudorandomness, an attacker can take advantage of the cryptographically insecure nature of this function to enumerate session tokens for accounts that are not under his/her control This issue affects: Mautic Mautic versions prior to 3.3.4; versions prior to 4.0.0.
## ✍️ Description The function mt_rand is used to generate session tokens, this function is cryptographically flawed due to its nature being one pseudorandomness, an attacker can take advantage of the cryptographically insecure nature of this function to enumerate session tokens for accounts that are not under his/her control ## 🕵️♂️ Proof of Concept Numerous examples and attack implementations can be found in this paper . If you're looking for a practical tool that can crack your mt_rand implementation's seed value, see this project and run the following commands in a console with php5 and OpenWall's tool installed: `root$ php -r 'mt_srand(13333337); echo mt_rand( ), "\n";'` After that, copy the output (1863134308) and execute the following commands: `root$ gcc php_mt_seed.c -o php_mt_seedroot$ ./php_mt_seed 1863134308` After waiting ~1 minute you should have a few possible seeds corresponding to their PHP versions, next to your installed PHP version you should see something akin to: seed = 0x00cb7359 = 13333337 (PHP 7.1.0+) Hey, that's your seed! ## 💥 Impact An attacker could takeover accounts at random by enumerating and using access tokens. ## 📝 References - https://openwall.com/php_mt_seedhttps://crypto.di.uoa.gr/CRYPTO.SEC/Randomness_Attacks_files/paper.pdf - https://github.com/mautic/mautic/blob/5213e320b4ef4d0c51bb84c1d46a1071e8e4f7fc/app/bundles/PointBundle/Controller/TriggerController.php#L187 - https://github.com/mautic/mautic/releases/tag/3.3.4 - https://github.com/mautic/mautic/releases/tag/4.0.0
## ✍️ Description The function mt_rand is used to generate session tokens, this function is cryptographically flawed due to its nature being one pseudorandomness, an attacker can take advantage of the cryptographically insecure nature of this function to enumerate session tokens for accounts that are not under his/her control ## 🕵️♂️ Proof of Concept Numerous examples and attack implementations can be found in this paper . If you're looking for a practical tool that can crack your mt_rand implementation's seed value, see this project and run the following commands in a console with php5 and OpenWall's tool installed: `root$ php -r 'mt_srand(13333337); echo mt_rand( ), "\n";'` After that, copy the output (1863134308) and execute the following commands: `root$ gcc php_mt_seed.c -o php_mt_seedroot$ ./php_mt_seed 1863134308` After waiting ~1 minute you should have a few possible seeds corresponding to their PHP versions, next to your installed PHP version you should see something akin to: seed = 0x00cb7359 = 13333337 (PHP 7.1.0+) Hey, that's your seed! ## 💥 Impact An attacker could takeover accounts at random by enumerating and using access tokens. ## 📝 References - https://openwall.com/php_mt_seedhttps://crypto.di.uoa.gr/CRYPTO.SEC/Randomness_Attacks_files/paper.pdf - https://github.com/mautic/mautic/blob/5213e320b4ef4d0c51bb84c1d46a1071e8e4f7fc/app/bundles/PointBundle/Controller/TriggerController.php#L187 - https://github.com/mautic/mautic/releases/tag/3.3.4 - https://github.com/mautic/mautic/releases/tag/4.0.0
La función mt_rand es usada para generar tokens de sesión, esta función es criptográficamente defectuosa debido a que su naturaleza es una pseudoaleatoriedad, un atacante puede aprovechar la naturaleza criptográficamente no segura de esta función para enumerar tokens de sesión para cuentas que no están bajo su control. Este problema afecta a: Mautic versiones anteriores a 3.3.4; versiones anteriores a 4.0.0.
| Version | Type | Source | Base | Exp | Impact | Vector |
|---|---|---|---|---|---|---|
| 2.0 | Primary | NVD | 3.5 | 6.8 | 2.9 | AV:N/AC:M/Au:S/C:P/I:N/A:N |
| 3.1 | Primary | cve.org | 3.5 | — | — | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L |
| 3.1 | Primary | NVD | 3.5 | 2.1 | 1.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N |
| 3.1 | Primary | cve.org | 3.5 | — | — | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L |
| 3.1 | Secondary | NVD | 3.5 | 2.1 | 1.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L |
| 3.1 | Secondary | GHSA | 3.5 | — | — | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L |