Skip to main content
← All vulnerabilities
CVE-2019-10912GHSA-W2FR-65VP-MXW3

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

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 3.4.26, 4.1.12, 4.2.7, 2.8.50, 9.5.8
None on Exploit-DB, Metasploit or GitHub

Summary

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.

Timeline

  1. CVE published
  2. Record last updated

Affected versions

  • n/a n/a

    Version range not reported

  • symfony/cachePackagist

    From 3.1.0 · fixed in 3.4.26

  • symfony/cachePackagist

    From 4.0.0 · fixed in 4.1.12

  • symfony/cachePackagist

    From 4.2.0 · fixed in 4.2.7

  • symfony/phpunit-bridgePackagist

    From 2.8.0 · fixed in 2.8.50

  • symfony/phpunit-bridgePackagist

    From 3.0.0 · fixed in 3.4.26

  • symfony/phpunit-bridgePackagist

    From 4.0.0 · fixed in 4.1.12

  • symfony/phpunit-bridgePackagist

    From 4.2.0 · fixed in 4.2.7

  • symfony/symfonyPackagist

    From 2.8.0 · fixed in 2.8.50

  • symfony/symfonyPackagist

    From 3.0.0 · fixed in 3.4.26

  • symfony/symfonyPackagist

    From 4.0.0 · fixed in 4.1.12

  • symfony/symfonyPackagist

    From 4.2.0 · fixed in 4.2.7

  • typo3/cms-corePackagist

    From 9.0.0 · fixed in 9.5.8

  • typo3/cmsPackagist

    From 9.0.0 · fixed in 9.5.8

References 13

symfony.com

lists.fedoraproject.org

debian.org

seclists.org

GitHub · symfony/symfony

typo3.org