CVE-2010-3666: Medium severity Typo3 TYPO3 vulnerability

Published Nov 4, 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.

Other sources

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.

Affected Software

9 affected componentsFixes available
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

Event History

Nov 4, 2019
CVE Published
via MITRE·09:27 PM
Data Sourced
via MITRE·09:27 PM
Description
Apr 21, 2022
Advisory Published
via GitHub·01:57 AM

Frequently Asked Questions

1

What is the severity of CVE-2010-3666?

CVE-2010-3666 has a medium severity level due to the insecure randomness in the uniqid function.

2

How do I fix CVE-2010-3666?

To mitigate CVE-2010-3666, upgrade TYPO3 to version 4.4.1, 4.3.4, 4.2.13, or 4.1.14.

3

What versions of TYPO3 are affected by CVE-2010-3666?

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.

4

Is CVE-2010-3666 related to randomness?

Yes, CVE-2010-3666 is specifically related to the insecure randomness in the uniqid function used in TYPO3.

5

What should I do if I can't upgrade due to compatibility issues with CVE-2010-3666?

If upgrading is not possible, consider applying security best practices for web applications and monitoring for vulnerabilities.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203