CVE-2010-3667: Input Validation
Published Nov 4, 2019
·Updated
TYPO3 before 4.1.14, 4.2.x before 4.2.13, 4.3.x before 4.3.4 and 4.4.x before 4.4.1 allows Spam Abuse in the native form content element.
Affected Software
9 affected componentsFixes available
composer/typo3/cms-frontend>=4.4.0<4.4.1
4.4.1
composer/typo3/cms-frontend>=4.3.0<4.3.4
4.3.4
composer/typo3/cms-frontend>=4.2.0<4.2.13
4.2.13
composer/typo3/cms-frontend<4.1.14
4.1.14
debian/typo3-src
Typo3 TYPO3>=4.4.0<4.4.1
Typo3 TYPO3>=4.3.0<4.3.4
Typo3 TYPO3<4.1.14
Typo3 TYPO3>=4.2.0<4.2.13
Event History
Nov 4, 2019
CVE Published
via MITRE·09:58 PM
Data Sourced
via MITRE·09:58 PM
Description
Apr 21, 2022
Advisory Published
via GitHub·01:57 AM
Frequently Asked Questions
1
What is the severity of CVE-2010-3667?
CVE-2010-3667 is considered to have a medium severity due to the potential for spam abuse through the native form content element.
2
Which TYPO3 versions are affected by CVE-2010-3667?
CVE-2010-3667 affects TYPO3 versions before 4.1.14, 4.2.x before 4.2.13, 4.3.x before 4.3.4, and 4.4.x before 4.4.1.
3
How do I fix CVE-2010-3667?
To fix CVE-2010-3667, upgrade to TYPO3 versions 4.1.14, 4.2.13, 4.3.4, or 4.4.1 or higher.
4
What kind of vulnerabilities does CVE-2010-3667 allow attackers to exploit?
CVE-2010-3667 allows attackers to exploit spam abuse in the form content element of TYPO3.
5
Is there a workaround for CVE-2010-3667?
There is no documented workaround for CVE-2010-3667; the only solution is to upgrade to a secure version.