First published: Mon Nov 04 2019(Updated: )
TYPO3 before 4.1.14, 4.2.x before 4.2.13, 4.3.x before 4.3.4 and 4.4.x before 4.4.1 contains insecure randomness in the `uniqid` function.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
composer/typo3/cms-install | >=4.4.0<4.4.1 | 4.4.1 |
composer/typo3/cms-install | >=4.3.0<4.3.4 | 4.3.4 |
composer/typo3/cms-install | >=4.2.0<4.2.13 | 4.2.13 |
composer/typo3/cms-install | <4.1.14 | 4.1.14 |
debian/typo3-src | ||
Typo3 Typo3 | >=4.4.0<4.4.1 | |
Typo3 Typo3 | >=4.3.0<4.3.4 | |
Typo3 Typo3 | <4.1.14 | |
Typo3 Typo3 | >=4.2.0<4.2.13 | |
TYPO3 | <4.1.14 | |
TYPO3 | >=4.2.0<4.2.13 | |
TYPO3 | >=4.3.0<4.3.4 | |
TYPO3 | >=4.4.0<4.4.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2010-3666 has a medium severity level due to the insecure randomness in the uniqid function.
To mitigate CVE-2010-3666, upgrade TYPO3 to version 4.4.1, 4.3.4, 4.2.13, or 4.1.14.
CVE-2010-3666 affects TYPO3 versions before 4.1.14, 4.2.x before 4.2.13, 4.3.x before 4.3.4, and 4.4.x before 4.4.1.
Yes, CVE-2010-3666 is specifically related to the insecure randomness in the uniqid function used in TYPO3.
If upgrading is not possible, consider applying security best practices for web applications and monitoring for vulnerabilities.