CVE-2009-3631: TYPO3 Backend Command Injection via Shell Metacharacters in Uploaded File Name

Published Nov 2, 2009
·
Updated

The Backend subcomponent in TYPO3 4.0.13 and earlier, 4.1.x before 4.1.13, 4.2.x before 4.2.10, and 4.3.x before 4.3beta2, when the DAM extension or ftp upload is enabled, allows remote authenticated users to execute arbitrary commands via shell metacharacters in a filename.

Other sources

TYPO3 Backend Command Injection via Shell Metacharacters in Uploaded File Name

— Packagist

Affected Software

67 affected componentsFixes available
composer/typo3/cms-backend>=4.3alpha1<4.3beta2
4.3beta2
composer/typo3/cms-backend>=4.2.0<4.2.10
4.2.10
composer/typo3/cms-backend>=4.1.0<4.1.13
4.1.13
composer/typo3/cms-backend<=4.0.13
Typo3 TYPO3<=4.0.12
Typo3 TYPO3=0.1.2
Typo3 TYPO3=1.0.14
Typo3 TYPO3=1.1
Typo3 TYPO3=1.1.1
Typo3 TYPO3=1.1.09
Typo3 TYPO3=1.1.10
Typo3 TYPO3=1.2.0
Typo3 TYPO3=1.3.0
Typo3 TYPO3=1.3.2
Typo3 TYPO3=3.0
Typo3 TYPO3=3.3.x
Typo3 TYPO3=3.5
Typo3 TYPO3=3.5.x
Typo3 TYPO3=3.6.x
Typo3 TYPO3=3.7.0
Typo3 TYPO3=3.7.1
Typo3 TYPO3=3.7.x
Typo3 TYPO3=3.8
Typo3 TYPO3=3.8.x
Typo3 TYPO3=4.0
Typo3 TYPO3=4.0.1
Typo3 TYPO3=4.0.2
Typo3 TYPO3=4.0.3
Typo3 TYPO3=4.0.4
Typo3 TYPO3=4.0.5
Typo3 TYPO3=4.0.6
Typo3 TYPO3=4.0.7
Typo3 TYPO3=4.0.8
Typo3 TYPO3=4.0.9
Typo3 TYPO3=4.0.10
Typo3 TYPO3=4.0.11
Typo3 TYPO3=4.1.0
Typo3 TYPO3=4.1.0-beta1
Typo3 TYPO3=4.1.0-rc1
Typo3 TYPO3=4.1.1
Typo3 TYPO3=4.1.2
Typo3 TYPO3=4.1.3
Typo3 TYPO3=4.1.4
Typo3 TYPO3=4.1.5
Typo3 TYPO3=4.1.6
Typo3 TYPO3=4.1.7
Typo3 TYPO3=4.1.8
Typo3 TYPO3=4.1.9
Typo3 TYPO3=4.1.10
Typo3 TYPO3=4.1.11
Typo3 TYPO3=4.1.12
Typo3 TYPO3=4.2.0
Typo3 TYPO3=4.2.1
Typo3 TYPO3=4.2.2
Typo3 TYPO3=4.2.3
Typo3 TYPO3=4.2.4
Typo3 TYPO3=4.2.5
Typo3 TYPO3=4.2.6
Typo3 TYPO3=4.2.7
Typo3 TYPO3=4.2.8
Typo3 TYPO3=4.2.9
Typo3 TYPO3=4.3
Typo3 TYPO3=4.3-alpha1
composer/typo3/cms-backend>=4.3alpha1, <4.3beta2
4.3beta2
composer/typo3/cms-backend>=4.2.0, <4.2.10
4.2.10
composer/typo3/cms-backend>=4.1.0, <4.1.13
4.1.13
composer/typo3/cms-backend<=4.0.13

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/typo3/cms-backend to a version that resolves this vulnerability.

    Fixed in 4.3beta2
  2. Upgrade

    Upgrade composer/typo3/cms-backend to a version that resolves this vulnerability.

    Fixed in 4.2.10
  3. Upgrade

    Upgrade composer/typo3/cms-backend to a version that resolves this vulnerability.

    Fixed in 4.1.13
  4. Upgrade

    Upgrade TYPO3 to a version that resolves this vulnerability.

    Fixed in 4.1.13
  5. Upgrade

    Upgrade TYPO3 to a version that resolves this vulnerability.

    Fixed in 4.2.10
  6. Upgrade

    Upgrade TYPO3 to a version that resolves this vulnerability.

    Fixed in 4.3beta2

Event History

Nov 2, 2009
CVE Published
via MITRE·03:00 PM
Data Sourced
via MITRE·03:00 PM
Description
Data Sourced
via NVD·03:30 PM
RemedyDescriptionSeverityWeaknessAffected Software
May 2, 2022
Advisory Published
via GitHub·03:46 AM
Data Sourced
via Packagist·03:46 AM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2009-3631?

CVE-2009-3631 is considered a high severity vulnerability due to its potential for remote command execution by authenticated users.

2

How do I fix CVE-2009-3631?

To fix CVE-2009-3631, update TYPO3 CMS to at least version 4.3beta2, 4.2.10, or 4.1.13.

3

Which TYPO3 versions are affected by CVE-2009-3631?

CVE-2009-3631 affects TYPO3 versions up to 4.3beta2, 4.2.9, and 4.1.12.

4

What type of attack does CVE-2009-3631 enable?

CVE-2009-3631 enables authenticated remote users to execute arbitrary commands through crafted filenames.

5

Is CVE-2009-3631 related to file uploads in TYPO3?

Yes, CVE-2009-3631 specifically involves vulnerabilities related to file uploads when the DAM extension or FTP upload is enabled.

Company

Resources

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