CVE-2010-3667: TYPO3 is vulnerable to Spam Abuse in the native form content element
5.3
CVSS Score
3.1
Basic Information
CVE ID
GHSA ID
EPSS Score
0.54274%
CWE
Published
4/21/2022
Updated
2/6/2024
KEV Status
No
Technology
PHP
PHPTechnical Details
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
| Package Name | Ecosystem | Vulnerable Versions | First Patched Version |
|---|---|---|---|
| typo3/cms-frontend | composer | < 4.1.14 | 4.1.14 |
| typo3/cms-frontend | composer | >= 4.2.0, < 4.2.13 | 4.2.13 |
| typo3/cms-frontend | composer | >= 4.3.0, < 4.3.4 | 4.3.4 |
| typo3/cms-frontend | composer | >= 4.4.0, < 4.4.1 | 4.4.1 |
Vulnerability Intelligence
Miggo AI
Miggo AIRoot Cause Analysis
The vulnerability stemmed from insufficient validation of the 'auto_respond_msg' parameter in TYPO3's form handling. The patches introduced HMAC checks to prevent tampering with this field. The t3lib_formmail::start() function previously accepted unverified 'auto_respond_msg' values, while tslib_content::FORM() failed to include the required HMAC field in forms. These omissions allowed attackers to inject arbitrary email targets by manipulating the form's hidden fields. The commit diffs explicitly show the addition of HMAC validation in these functions to address the vulnerability.