First published: Tue Nov 05 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 is open to a session fixation attack which allows remote attackers to hijack a victim's session.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
composer/typo3/cms-install | >=4.4.0<4.4.1 | 4.4.1 |
composer/typo3/cms-install | >=4.3.0<4.3.4 | 4.3.4 |
composer/typo3/cms-install | >=4.2.0<4.2.13 | 4.2.13 |
composer/typo3/cms-install | <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 | |
TYPO3 | <4.1.14 | |
TYPO3 | >=4.2.0<4.2.13 | |
TYPO3 | >=4.3.0<4.3.4 | |
TYPO3 | >=4.4.0<4.4.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2010-3671 has a high severity due to the potential for session fixation attacks that can lead to session hijacking.
To fix CVE-2010-3671, upgrade TYPO3 to version 4.4.1 or later, 4.3.4 or later, 4.2.13 or later, or 4.1.14.
CVE-2010-3671 affects TYPO3 versions prior to 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.
CVE-2010-3671 is a vulnerability that allows session fixation attacks, enabling attackers to hijack user sessions.
Yes, CVE-2010-3671 is considered critical as it poses a significant risk of session hijacking for web applications using vulnerable versions of TYPO3.