First published: Wed Sep 05 2012(Updated: )
The configuration module in the backend in TYPO3 4.5.x before 4.5.19, 4.6.x before 4.6.12 and 4.7.x before 4.7.4 allows remote authenticated backend users to obtain the encryption key via unspecified vectors.
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
composer/typo3/cms | >=4.7<4.7.4 | 4.7.4 |
composer/typo3/cms | >=4.6<4.6.12 | 4.6.12 |
composer/typo3/cms | >=4.5<4.5.19 | 4.5.19 |
TYPO3 | =4.5 | |
TYPO3 | =4.5.0 | |
TYPO3 | =4.5.1 | |
TYPO3 | =4.5.2 | |
TYPO3 | =4.5.3 | |
TYPO3 | =4.5.4 | |
TYPO3 | =4.5.5 | |
TYPO3 | =4.5.6 | |
TYPO3 | =4.5.7 | |
TYPO3 | =4.5.8 | |
TYPO3 | =4.5.9 | |
TYPO3 | =4.5.10 | |
TYPO3 | =4.5.11 | |
TYPO3 | =4.5.12 | |
TYPO3 | =4.5.13 | |
TYPO3 | =4.5.14 | |
TYPO3 | =4.5.15 | |
TYPO3 | =4.5.16 | |
TYPO3 | =4.5.17 | |
TYPO3 | =4.5.18 | |
TYPO3 | =4.6 | |
TYPO3 | =4.6.0 | |
TYPO3 | =4.6.1 | |
TYPO3 | =4.6.2 | |
TYPO3 | =4.6.3 | |
TYPO3 | =4.6.4 | |
TYPO3 | =4.6.5 | |
TYPO3 | =4.6.6 | |
TYPO3 | =4.6.7 | |
TYPO3 | =4.6.8 | |
TYPO3 | =4.6.9 | |
TYPO3 | =4.6.10 | |
TYPO3 | =4.6.11 | |
TYPO3 | =4.7 | |
TYPO3 | =4.7.0 | |
TYPO3 | =4.7.1 | |
TYPO3 | =4.7.2 | |
TYPO3 | =4.7.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2012-3529 is considered high due to the risk of exposing sensitive encryption keys to remote authenticated users.
To fix CVE-2012-3529, update TYPO3 to version 4.5.19, 4.6.12, or 4.7.4 or later.
CVE-2012-3529 affects TYPO3 versions 4.5.x prior to 4.5.19, 4.6.x prior to 4.6.12, and 4.7.x prior to 4.7.4.
CVE-2012-3529 is a security vulnerability that allows unauthorized exposure of encryption keys.
Yes, CVE-2012-3529 can be exploited by remote authenticated backend users.