CVE-2010-3714: High severity Typo3 TYPO3 vulnerability

Published Oct 25, 2010
·
Updated

The jumpUrl (aka access tracking) implementation in tslib/class.tslibfe.php in TYPO3 4.2.x before 4.2.15, 4.3.x before 4.3.7, and 4.4.x before 4.4.4 does not properly compare certain hash values during access-control decisions, which allows remote attackers to read arbitrary files via unspecified vectors.

Other sources

The jumpUrl (aka access tracking) implementation in tslib/class.tslibfe.php in TYPO3 4.2.x before 4.2.15, 4.3.x before 4.3.7, and 4.4.x before 4.4.4 does not properly compare certain hash values during access-control decisions, which allows remote attackers to read arbitrary files via unspecified vectors.

Affected Software

29 affected componentsFixes available
composer/typo3/cms>=4.4.0<4.4.4
4.4.4
composer/typo3/cms>=4.3.0<4.3.7
4.3.7
composer/typo3/cms>=4.2.0<4.2.15
4.2.15
Typo3 TYPO3=4.2.10
Typo3 TYPO3=4.3.6
Typo3 TYPO3=4.2.14
Typo3 TYPO3=4.3.5
Typo3 TYPO3=4.2.4
Typo3 TYPO3=4.2.5
Typo3 TYPO3=4.2.11
Typo3 TYPO3=4.2.0
Typo3 TYPO3=4.2.8
Typo3 TYPO3=4.2.13
Typo3 TYPO3=4.2.3
Typo3 TYPO3=4.2.1
Typo3 TYPO3=4.3.2
Typo3 TYPO3=4.4.1
Typo3 TYPO3=4.4.2
Typo3 TYPO3=4.2.12
Typo3 TYPO3=4.2.6
Typo3 TYPO3=4.3.0
Typo3 TYPO3=4.2.2
Typo3 TYPO3=4.3.3
Typo3 TYPO3=4.3.4
Typo3 TYPO3=4.4
Typo3 TYPO3=4.3.1
Typo3 TYPO3=4.2.7
Typo3 TYPO3=4.4.3
Typo3 TYPO3=4.2.9

Event History

Oct 25, 2010
CVE Published
via MITRE·07:00 PM
Data Sourced
via MITRE·07:00 PM
Description
May 17, 2022
Advisory Published
via GitHub·05:28 AM

Frequently Asked Questions

1

What is the severity of CVE-2010-3714?

CVE-2010-3714 has a medium severity rating due to its potential to allow unauthorized access to sensitive files.

2

How do I fix CVE-2010-3714?

To fix CVE-2010-3714, upgrade TYPO3 to version 4.2.15, 4.3.7, or 4.4.4 or later.

3

Which TYPO3 versions are affected by CVE-2010-3714?

TYPO3 versions 4.2.x before 4.2.15, 4.3.x before 4.3.7, and 4.4.x before 4.4.4 are affected by CVE-2010-3714.

4

Can CVE-2010-3714 lead to data breaches?

Yes, CVE-2010-3714 could potentially allow remote attackers to read arbitrary files, leading to data breaches.

5

Is there a workaround for CVE-2010-3714 if I can't upgrade?

There are no effective workarounds for CVE-2010-3714, so upgrading to a secure version is strongly recommended.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203