CVE-2014-3945: Medium severity Typo3 TYPO3 vulnerability

Published Jun 3, 2014
·
Updated

The Authentication component in TYPO3 before 6.2, when salting for password hashing is disabled, does not require knowledge of the cleartext password if the password hash is known, which allows remote attackers to bypass authentication and gain access to the backend by leveraging knowledge of a password hash.

Affected Software

187 affected componentsFixes available
Typo3 TYPO3<=6.1.9
Typo3 TYPO3=4.0
Typo3 TYPO3=4.0.0
Typo3 TYPO3=4.0.1
Typo3 TYPO3=4.0.2
Typo3 TYPO3=4.0.3
Typo3 TYPO3=4.0.4
Typo3 TYPO3=4.0.5
Typo3 TYPO3=4.0.6
Typo3 TYPO3=4.0.7
Typo3 TYPO3=4.0.8
Typo3 TYPO3=4.0.9
Typo3 TYPO3=4.0.10
Typo3 TYPO3=4.0.11
Typo3 TYPO3=4.0.12
Typo3 TYPO3=4.0.13
Typo3 TYPO3=4.1
Typo3 TYPO3=4.1.0
Typo3 TYPO3=4.1.1
Typo3 TYPO3=4.1.2
Typo3 TYPO3=4.1.3
Typo3 TYPO3=4.1.4
Typo3 TYPO3=4.1.5
Typo3 TYPO3=4.1.6
Typo3 TYPO3=4.1.7
Typo3 TYPO3=4.1.8
Typo3 TYPO3=4.1.9
Typo3 TYPO3=4.1.10
Typo3 TYPO3=4.1.11
Typo3 TYPO3=4.1.12
Typo3 TYPO3=4.1.13
Typo3 TYPO3=4.1.14
Typo3 TYPO3=4.1.15
Typo3 TYPO3=4.2
Typo3 TYPO3=4.2.0
Typo3 TYPO3=4.2.1
Typo3 TYPO3=4.2.2
Typo3 TYPO3=4.2.3
Typo3 TYPO3=4.2.4
Typo3 TYPO3=4.2.5
Typo3 TYPO3=4.2.6
Typo3 TYPO3=4.2.7
Typo3 TYPO3=4.2.8
Typo3 TYPO3=4.2.9
Typo3 TYPO3=4.2.10
Typo3 TYPO3=4.2.11
Typo3 TYPO3=4.2.12
Typo3 TYPO3=4.2.13
Typo3 TYPO3=4.2.14
Typo3 TYPO3=4.2.15
Typo3 TYPO3=4.2.16
Typo3 TYPO3=4.2.17
Typo3 TYPO3=4.3
Typo3 TYPO3=4.3.0
Typo3 TYPO3=4.3.1
Typo3 TYPO3=4.3.2
Typo3 TYPO3=4.3.3
Typo3 TYPO3=4.3.4
Typo3 TYPO3=4.3.5
Typo3 TYPO3=4.3.6
Typo3 TYPO3=4.3.7
Typo3 TYPO3=4.3.8
Typo3 TYPO3=4.3.9
Typo3 TYPO3=4.3.10
Typo3 TYPO3=4.3.11
Typo3 TYPO3=4.3.12
Typo3 TYPO3=4.3.13
Typo3 TYPO3=4.3.14
Typo3 TYPO3=4.4
Typo3 TYPO3=4.4.0
Typo3 TYPO3=4.4.1
Typo3 TYPO3=4.4.2
Typo3 TYPO3=4.4.3
Typo3 TYPO3=4.4.4
Typo3 TYPO3=4.4.5
Typo3 TYPO3=4.4.6
Typo3 TYPO3=4.4.7
Typo3 TYPO3=4.4.8
Typo3 TYPO3=4.4.9
Typo3 TYPO3=4.4.10
Typo3 TYPO3=4.4.11
Typo3 TYPO3=4.4.12
Typo3 TYPO3=4.4.13
Typo3 TYPO3=4.4.14
Typo3 TYPO3=4.4.15
Typo3 TYPO3=4.5
Typo3 TYPO3=4.5.0
Typo3 TYPO3=4.5.1
Typo3 TYPO3=4.5.2
Typo3 TYPO3=4.5.3
Typo3 TYPO3=4.5.4
Typo3 TYPO3=4.5.5
Typo3 TYPO3=4.5.6
Typo3 TYPO3=4.5.7
Typo3 TYPO3=4.5.8
Typo3 TYPO3=4.5.9
Typo3 TYPO3=4.5.10
Typo3 TYPO3=4.5.11
Typo3 TYPO3=4.5.12
Typo3 TYPO3=4.5.13
Typo3 TYPO3=4.5.14
Typo3 TYPO3=4.5.15
Typo3 TYPO3=4.5.16
Typo3 TYPO3=4.5.17
Typo3 TYPO3=4.5.18
Typo3 TYPO3=4.5.19
Typo3 TYPO3=4.5.20
Typo3 TYPO3=4.5.21
Typo3 TYPO3=4.5.22
Typo3 TYPO3=4.5.23
Typo3 TYPO3=4.5.24
Typo3 TYPO3=4.5.25
Typo3 TYPO3=4.5.26
Typo3 TYPO3=4.5.27
Typo3 TYPO3=4.5.28
Typo3 TYPO3=4.5.29
Typo3 TYPO3=4.5.30
Typo3 TYPO3=4.5.31
Typo3 TYPO3=4.5.32
Typo3 TYPO3=4.5.33
Typo3 TYPO3=4.5.34
Typo3 TYPO3=4.6
Typo3 TYPO3=4.6.0
Typo3 TYPO3=4.6.1
Typo3 TYPO3=4.6.2
Typo3 TYPO3=4.6.3
Typo3 TYPO3=4.6.4
Typo3 TYPO3=4.6.5
Typo3 TYPO3=4.6.6
Typo3 TYPO3=4.6.7
Typo3 TYPO3=4.6.8
Typo3 TYPO3=4.6.9
Typo3 TYPO3=4.6.10
Typo3 TYPO3=4.6.11
Typo3 TYPO3=4.6.12
Typo3 TYPO3=4.6.13
Typo3 TYPO3=4.6.14
Typo3 TYPO3=4.6.15
Typo3 TYPO3=4.6.16
Typo3 TYPO3=4.6.17
Typo3 TYPO3=4.6.18
Typo3 TYPO3=4.7
Typo3 TYPO3=4.7.0
Typo3 TYPO3=4.7.1
Typo3 TYPO3=4.7.2
Typo3 TYPO3=4.7.3
Typo3 TYPO3=4.7.4
Typo3 TYPO3=4.7.5
Typo3 TYPO3=4.7.6
Typo3 TYPO3=4.7.7
Typo3 TYPO3=4.7.8
Typo3 TYPO3=4.7.9
Typo3 TYPO3=4.7.10
Typo3 TYPO3=4.7.11
Typo3 TYPO3=4.7.12
Typo3 TYPO3=4.7.13
Typo3 TYPO3=4.7.14
Typo3 TYPO3=4.7.15
Typo3 TYPO3=4.7.16
Typo3 TYPO3=4.7.17
Typo3 TYPO3=4.7.18
Typo3 TYPO3=4.7.19
Typo3 TYPO3=6.0
Typo3 TYPO3=6.0.1
Typo3 TYPO3=6.0.2
Typo3 TYPO3=6.0.3
Typo3 TYPO3=6.0.4
Typo3 TYPO3=6.0.5
Typo3 TYPO3=6.0.6
Typo3 TYPO3=6.0.7
Typo3 TYPO3=6.0.8
Typo3 TYPO3=6.0.9
Typo3 TYPO3=6.0.10
Typo3 TYPO3=6.0.11
Typo3 TYPO3=6.0.12
Typo3 TYPO3=6.0.13
Typo3 TYPO3=6.0.14
Typo3 TYPO3=6.1
Typo3 TYPO3=6.1.1
Typo3 TYPO3=6.1.2
Typo3 TYPO3=6.1.3
Typo3 TYPO3=6.1.4
Typo3 TYPO3=6.1.5
Typo3 TYPO3=6.1.6
Typo3 TYPO3=6.1.7
Typo3 TYPO3=6.1.8
composer/typo3/cms<6.2.0
6.2.0

Event History

Jun 3, 2014
CVE Published
via MITRE·02:00 PM
Data Sourced
via MITRE·02:00 PM
Description
Data Sourced
via NVD·02:55 PM
DescriptionSeverityWeaknessAffected Software
May 17, 2022
Advisory Published
via GitHub·04:42 AM

Frequently Asked Questions

1

What is the severity of CVE-2014-3945?

CVE-2014-3945 has a high severity rating due to its potential to allow unauthorized access to the backend of TYPO3 systems.

2

How do I fix CVE-2014-3945?

To fix CVE-2014-3945, upgrade TYPO3 to version 6.2 or later, where salting for password hashing is enabled by default.

3

When was CVE-2014-3945 disclosed?

CVE-2014-3945 was disclosed in June 2014 as part of a security bulletin from TYPO3.

4

Which versions of TYPO3 are affected by CVE-2014-3945?

CVE-2014-3945 affects TYPO3 versions before 6.2, specifically 6.1.9 and earlier.

5

What impact does CVE-2014-3945 have on TYPO3 applications?

CVE-2014-3945 allows attackers to bypass authentication and gain unauthorized access to the TYPO3 backend.

Company

Resources

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