Powermail EExtension up to 12.3.5 on TYPO3 confirmationAction resource injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.9 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Powermail EExtension up to 12.3.5 on TYPO3. The affected element is the function confirmationAction. Performing a manipulation of the argument mail results in resource injection.
This vulnerability is identified as CVE-2024-45232. The attack can be initiated remotely. There is not any exploit available.
It is recommended to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, was found in Powermail EExtension up to 12.3.5 on TYPO3. This affects the function confirmationAction. The manipulation of the argument mail with an unknown input leads to a resource injection vulnerability. CWE is classifying the issue as CWE-99. The product receives input from an upstream component, but it does not restrict or incorrectly restricts the input before it is used as an identifier for a resource that may be outside the intended sphere of control. This is going to have an impact on confidentiality. The summary by CVE is:
An issue was discovered in powermail extension through 12.3.5 for TYPO3. It fails to validate the mail parameter of the confirmationAction, resulting in Insecure Direct Object Reference (IDOR). An unauthenticated attacker can use this to display the user-submitted data of all forms persisted by the extension. This can only be exploited when the extension is configured to save submitted form data to the database (plugin.tx_powermail.settings.db.enable=1), which however is the default setting of the extension. The fixed versions are 7.5.0, 8.5.0, 10.9.0, and 12.4.0
It is possible to read the advisory at typo3.org. This vulnerability is uniquely identified as CVE-2024-45232 since 08/24/2024. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 7.5.0, 8.5.0, 10.9.0 or 12.4.0 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.0VulDB Meta Temp Score: 5.9
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
NVD Vector: 🔍
CNA Base Score: 7.3
CNA Vector (MITRE): 🔍
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: Resource injectionCWE: CWE-99
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Powermail EExtension 7.5.0/8.5.0/10.9.0/12.4.0
Timeline
08/24/2024 🔍08/29/2024 🔍
08/29/2024 🔍
08/31/2024 🔍
Sources
Advisory: typo3.orgStatus: Confirmed
CVE: CVE-2024-45232 (🔍)
GCVE (CVE): GCVE-0-2024-45232
GCVE (VulDB): GCVE-100-276051
Entry
Created: 08/29/2024 06:57Updated: 08/31/2024 03:19
Changes: 08/29/2024 06:57 (55), 08/29/2024 15:31 (1), 08/31/2024 03:19 (20)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.