CVE-2019-10912: Prevent destructors with side-effects from being unserialized

Published Apr 16, 2019
·
Updated

CVE-2019-10912: Prevent destructors with side-effects from being unserialized

Other sources

In Symfony before 2.8.50, 3.x before 3.4.26, 4.x before 4.1.12, and 4.2.x before 4.2.7, it is possible to cache objects that may contain bad user input. On serialization or unserialization, this could result in the deletion of files that the current user has access to. This is related to symfony/cache and symfony/phpunit-bridge.

Possible deserialization side-effects in symfony/cache

Affected Software

50 affected componentsFixes available
composer/typo3/cms-core>=9.0.0, <9.5.8
composer/symfony/cache>=3.1.0, <3.2.0, >=3.2.0, <3.3.0, >=3.3.0, <3.4.0, >=3.4.0, <3.4.26, >=4.0.0, <4.1.0, >=4.1.0, <4.1.12, >=4.2.0, <4.2.7
composer/symfony/symfony>=2.8.0, <2.8.50, >=3.0.0, <3.1.0, >=3.1.0, <3.2.0, >=3.2.0, <3.3.0, >=3.3.0, <3.4.0, >=3.4.0, <3.4.26, >=4.0.0, <4.1.0, >=4.1.0, <4.1.12, >=4.2.0, <4.2.7
composer/symfony/phpunit-bridge>=2.8.0, <2.8.50, >=3.0.0, <3.1.0, >=3.1.0, <3.2.0, >=3.2.0, <3.3.0, >=3.3.0, <3.4.0, >=3.4.0, <3.4.26, >=4.0.0, <4.1.0, >=4.1.0, <4.1.12, >=4.2.0, <4.2.7
composer/typo3/cms>=9.0.0, <9.5.8
debian/symfony
3.4.22+dfsg-2+deb10u13.4.22+dfsg-2+deb10u24.4.19+dfsg-2+deb11u35.4.23+dfsg-15.4.29+dfsg-15.4.30+dfsg-1
composer/typo3/cms>=9.0.0<9.5.8
9.5.8
composer/typo3/cms-core>=9.0.0<9.5.8
9.5.8
composer/symfony/symfony>=4.2.0<4.2.7
4.2.7
composer/symfony/symfony>=4.0.0<4.1.12
4.1.12
composer/symfony/symfony>=3.0.0<3.4.26
3.4.26
composer/symfony/symfony>=2.8.0<2.8.50
2.8.50
composer/symfony/phpunit-bridge>=4.2.0<4.2.7
4.2.7
composer/symfony/phpunit-bridge>=4.0.0<4.1.12
4.1.12
composer/symfony/phpunit-bridge>=3.0.0<3.4.26
3.4.26
composer/symfony/phpunit-bridge>=2.8.0<2.8.50
2.8.50
composer/symfony/cache>=4.2.0<4.2.7
4.2.7
composer/symfony/cache>=4.0.0<4.1.12
4.1.12
composer/symfony/cache>=3.1.0<3.4.26
3.4.26
SensioLabs Symfony>=2.8.0<2.8.50
SensioLabs Symfony>=3.4.0<3.4.26
SensioLabs Symfony>=4.1.0<4.1.12
SensioLabs Symfony>=4.2.0<4.2.7
composer/symfony/symfony>=2.8.0, <2.8.50
2.8.50
composer/symfony/symfony>=3.0.0, <3.1.0
composer/symfony/symfony>=3.1.0, <3.2.0
composer/symfony/symfony>=3.2.0, <3.3.0
composer/symfony/symfony>=3.3.0, <3.4.0
composer/symfony/symfony>=3.4.0, <3.4.26
3.4.26
composer/symfony/symfony>=4.0.0, <4.1.0
composer/symfony/symfony>=4.1.0, <4.1.12
4.1.12
composer/symfony/symfony>=4.2.0, <4.2.7
4.2.7
composer/typo3/cms-core>=9.0.0, <9.5.8
9.5.8
composer/symfony/cache>=3.1.0, <3.2.0
composer/symfony/cache>=3.2.0, <3.3.0
composer/symfony/cache>=3.3.0, <3.4.0
composer/symfony/cache>=3.4.0, <3.4.26
3.4.26
composer/symfony/cache>=4.0.0, <4.1.0
composer/symfony/cache>=4.1.0, <4.1.12
4.1.12
composer/symfony/cache>=4.2.0, <4.2.7
4.2.7
composer/typo3/cms>=9.0.0, <9.5.8
9.5.8
composer/symfony/phpunit-bridge>=2.8.0, <2.8.50
2.8.50
composer/symfony/phpunit-bridge>=3.0.0, <3.1.0
composer/symfony/phpunit-bridge>=3.1.0, <3.2.0
composer/symfony/phpunit-bridge>=3.2.0, <3.3.0
composer/symfony/phpunit-bridge>=3.3.0, <3.4.0
composer/symfony/phpunit-bridge>=3.4.0, <3.4.26
3.4.26
composer/symfony/phpunit-bridge>=4.0.0, <4.1.0
composer/symfony/phpunit-bridge>=4.1.0, <4.1.12
4.1.12
composer/symfony/phpunit-bridge>=4.2.0, <4.2.7
4.2.7

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/symfony to a version that resolves this vulnerability.

    Fixed in 3.4.22+dfsg-2+deb10u1Fixed in 3.4.22+dfsg-2+deb10u2Fixed in 4.4.19+dfsg-2+deb11u3Fixed in 5.4.23+dfsg-1Fixed in 5.4.29+dfsg-1Fixed in 5.4.30+dfsg-1
  2. Upgrade

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

    Fixed in 9.5.8
  3. Upgrade

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

    Fixed in 9.5.8
  4. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 4.2.7
  5. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 4.1.12
  6. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 3.4.26
  7. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 2.8.50
  8. Upgrade

    Upgrade composer/symfony/phpunit-bridge to a version that resolves this vulnerability.

    Fixed in 4.2.7
  9. Upgrade

    Upgrade composer/symfony/phpunit-bridge to a version that resolves this vulnerability.

    Fixed in 4.1.12
  10. Upgrade

    Upgrade composer/symfony/phpunit-bridge to a version that resolves this vulnerability.

    Fixed in 3.4.26
  11. Upgrade

    Upgrade composer/symfony/phpunit-bridge to a version that resolves this vulnerability.

    Fixed in 2.8.50
  12. Upgrade

    Upgrade composer/symfony/cache to a version that resolves this vulnerability.

    Fixed in 4.2.7
  13. Upgrade

    Upgrade composer/symfony/cache to a version that resolves this vulnerability.

    Fixed in 4.1.12
  14. Upgrade

    Upgrade composer/symfony/cache to a version that resolves this vulnerability.

    Fixed in 3.4.26

Event History

Apr 16, 2019
Advisory Published
11:01 AM
Data Sourced
via Packagist·11:01 AM
DescriptionSeverityAffected Software
May 16, 2019
CVE Published
via MITRE·09:20 PM
Data Sourced
via MITRE·09:20 PM
Description

Frequently Asked Questions

1

What is CVE-2019-10912?

CVE-2019-10912 is a vulnerability in Symfony before 2.8.50, 3.x before 3.4.26, 4.x before 4.1.12, and 4.2.x before 4.2.7 that allows caching of objects containing bad user input, leading to potential deletion of files.

2

What is the severity of CVE-2019-10912?

The severity of CVE-2019-10912 is high with a CVSS score of 7.1.

3

How can I fix CVE-2019-10912?

To fix CVE-2019-10912, update Symfony to version 2.8.50, 3.4.26, 4.1.12, or 4.2.7.

4

Where can I find more information about CVE-2019-10912?

More information about CVE-2019-10912 can be found at the TYPO3 security advisory (typo3.org/security/advisory/typo3-core-sa-2019-016) and the Symfony official website (symfony.com/cve-2019-10912 and symfony.com/blog/cve-2019-10912-prevent-destructors-with-side-effects-from-being-unserialized).

5

What is the CWE for CVE-2019-10912?

The CWE for CVE-2019-10912 is CWE-502: Deserialization of Untrusted Data.

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