TYPO3 4.7 File Upload tce_file.php cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in TYPO3 4.7. The impacted element is an unknown function of the file tce_file.php of the component File Upload. This manipulation causes cross-site request forgery. Remote exploitation of the attack is possible. Furthermore, an exploit is available.
Details
A vulnerability has been found in TYPO3 4.7 (Content Management System) and classified as critical. Affected by this vulnerability is an unknown code of the file tce_file.php of the component File Upload. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. The CWE definition for the vulnerability is CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was published 06/03/2012 by KedAns-Dz with Inj3ct0r 1337Team as File 113220/TYP as confirmed exploit (PacketStorm). The advisory is shared at packetstormsecurity.org. The public release happened without involvement of the project team. The exploitation appears to be easy. The attack can be launched remotely. A single authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details and also a public exploit are known.
A public exploit has been developed by KedAns-Dz in HTML and been published immediately after the advisory. It is possible to download the exploit at packetstormsecurity.org. It is declared as proof-of-concept. By approaching the search of inurl:tce_file.php it is possible to find vulnerable targets with Google Hacking.
Proper firewalling of tcp/80, tcp/443 is able to address this issue.
The vulnerability is also documented in the vulnerability database at OSVDB (82615†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
License
Website
- Product: https://typo3.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.0VulDB Meta Temp Score: 7.3
VulDB Base Score: 8.0
VulDB Temp Score: 7.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: 🔍
Exploiting
Class: Cross-site request forgeryCWE: CWE-352 / CWE-862 / CWE-863
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Author: KedAns-Dz
Programming Language: 🔍
Download: 🔍
Google Hack: 🔍
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Exploit Delay Time: 🔍
Firewalling: 🔍
Timeline
06/03/2012 🔍06/03/2012 🔍
06/05/2012 🔍
06/08/2012 🔍
04/27/2018 🔍
Sources
Product: typo3.orgAdvisory: File 113220/TYP
Researcher: KedAns-Dz
Organization: Inj3ct0r 1337Team
Status: Confirmed
GCVE (VulDB): GCVE-100-5485
OSVDB: 82615
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 06/08/2012 11:16Updated: 04/27/2018 09:21
Changes: 06/08/2012 11:16 (50), 04/27/2018 09:21 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.