TYPO3 up to 4.5.33/4.7.18/6.0.13/6.1.8/6.2.2 Authentication improper authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in TYPO3 up to 4.5.33/4.7.18/6.0.13/6.1.8/6.2.2 and classified as problematic. This vulnerability affects unknown code of the component Authentication. Such manipulation leads to improper authentication. This vulnerability is documented as CVE-2014-3945. Additionally, an exploit exists. It is suggested to upgrade the affected component.
Details
A vulnerability was found in TYPO3 up to 4.5.33/4.7.18/6.0.13/6.1.8/6.2.2 (Content Management System). It has been rated as problematic. Affected by this issue is an unknown code of the component Authentication. The manipulation with an unknown input leads to a improper authentication vulnerability. Using CWE to declare the problem leads to CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. Impacted is confidentiality, and integrity. CVE summarizes:
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.
The weakness was released 05/22/2014 by Helmut Hummel as TYPO3-CORE-SA-2014-001 as confirmed advisory (Website). The advisory is available at typo3.org. This vulnerability is handled as CVE-2014-3945 since 06/03/2014. The exploitation is known to be difficult. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details are unknown but a public exploit is available. The advisory points out:
When the use of salted password is disabled (which is enabled by default since TYPO3 4.6 and required since TYPO3 6.2) passwords for backend access are stored as md5 hash in the database. This hash (e.g. taken from a successful SQL injection) can be used directly to authenticate backend users without knowing or reverse engineering the password.
After before and not just, there has been an exploit disclosed. The exploit is available at skeletonscribe.net. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 386 days. During that time the estimated underground price was around $5k-$25k.
Upgrading to version 6.2 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability. The advisory contains the following remark:
In TYPO3 version 6.2 it is still possible to disable password salt hashing for frontend users. It should be apparent that such setup is insecure and not recommended.
The vulnerability is also documented in the databases at X-Force (93462), SecurityFocus (BID 67627†), Secunia (SA58901†) and Vulnerability Center (SBV-45081†). Entries connected to this vulnerability are available at VDB-13347, VDB-13345, VDB-13344 and VDB-13343. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Name
Version
- 4.5.0
- 4.5.1
- 4.5.2
- 4.5.3
- 4.5.4
- 4.5.5
- 4.5.6
- 4.5.7
- 4.5.8
- 4.5.9
- 4.5.10
- 4.5.11
- 4.5.12
- 4.5.13
- 4.5.14
- 4.5.15
- 4.5.16
- 4.5.17
- 4.5.18
- 4.5.19
- 4.5.20
- 4.5.21
- 4.5.22
- 4.5.23
- 4.5.24
- 4.5.25
- 4.5.26
- 4.5.27
- 4.5.28
- 4.5.29
- 4.5.30
- 4.5.31
- 4.5.32
- 4.5.33
- 4.7.0
- 4.7.1
- 4.7.2
- 4.7.3
- 4.7.4
- 4.7.5
- 4.7.6
- 4.7.7
- 4.7.8
- 4.7.9
- 4.7.10
- 4.7.11
- 4.7.12
- 4.7.13
- 4.7.14
- 4.7.15
- 4.7.16
- 4.7.17
- 4.7.18
- 6.0.0
- 6.0.1
- 6.0.2
- 6.0.3
- 6.0.4
- 6.0.5
- 6.0.6
- 6.0.7
- 6.0.8
- 6.0.9
- 6.0.10
- 6.0.11
- 6.0.12
- 6.0.13
- 6.1.0
- 6.1.1
- 6.1.2
- 6.1.3
- 6.1.4
- 6.1.5
- 6.1.6
- 6.1.7
- 6.1.8
- 6.2.0
- 6.2.1
- 6.2.2
License
Website
- Product: https://typo3.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.8VulDB Meta Temp Score: 4.3
VulDB Base Score: 4.8
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Improper authenticationCWE: CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: TYPO3 6.2
Timeline
05/01/2013 🔍05/22/2014 🔍
05/22/2014 🔍
05/22/2014 🔍
05/22/2014 🔍
05/23/2014 🔍
05/23/2014 🔍
06/03/2014 🔍
06/03/2014 🔍
06/22/2014 🔍
05/31/2017 🔍
Sources
Product: typo3.orgAdvisory: TYPO3-CORE-SA-2014-001
Researcher: Helmut Hummel
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2014-3945 (🔍)
GCVE (CVE): GCVE-0-2014-3945
GCVE (VulDB): GCVE-100-13346
X-Force: 93462 - TYPO3 authentication subcomponent security bypass, Medium Risk
SecurityFocus: 67627 - TYPO3 Authentication Subcomponent Security Bypass Vulnerability
Secunia: 58901 - TYPO3 Multiple Vulnerabilities, Moderately Critical
Vulnerability Center: 45081 - TYPO3 <6.2 Remote Security Bypass Vulnerability, Medium
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 05/23/2014 16:09Updated: 05/31/2017 08:57
Changes: 05/23/2014 16:09 (77), 05/31/2017 08:57 (4)
Complete: 🔍
Cache ID: 216:822:103
No comments yet. Languages: en.
Please log in to comment.