direct_mail Extension up to 5.2.3 on TYPO3 Log Entries allocation of resources
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in direct_mail Extension up to 5.2.3 on TYPO3. This issue affects some unknown processing. Such manipulation as part of Log Entries leads to allocation of resources. This vulnerability is uniquely identified as CVE-2020-12697. The attack can be launched remotely. No exploit exists.
Details
A vulnerability was found in direct_mail Extension up to 5.2.3 on TYPO3 and classified as problematic. Affected by this issue is some unknown functionality. The manipulation as part of a Log Entries leads to a allocation of resources vulnerability. Using CWE to declare the problem leads to CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. Impacted is availability. CVE summarizes:
The direct_mail extension through 5.2.3 for TYPO3 allows Denial of Service via log entries.
The weakness was disclosed 05/13/2020 (Website). The advisory is shared for download at typo3.org. This vulnerability is handled as CVE-2020-12697 since 05/07/2020. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1499.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-155193, VDB-155194 and VDB-155195 are pretty similar. VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
NVD Vector: 🔍
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: Allocation of resourcesCWE: CWE-770 / CWE-400 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
05/07/2020 🔍05/13/2020 🔍
05/14/2020 🔍
10/17/2020 🔍
Sources
Advisory: typo3.orgStatus: Not defined
Confirmation: 🔍
CVE: CVE-2020-12697 (🔍)
GCVE (CVE): GCVE-0-2020-12697
GCVE (VulDB): GCVE-100-155192
See also: 🔍
Entry
Created: 05/14/2020 08:28Updated: 10/17/2020 16:28
Changes: 05/14/2020 08:28 (38), 05/14/2020 08:33 (17), 10/17/2020 16:28 (1)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.