CVE Vulnerabilities

CVE-2019-10912

Deserialization of Untrusted Data

Published: May 16, 2019 | Modified: Nov 21, 2024
CVSS 3.x
7.1
HIGH
Source:
NVD
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N
CVSS 2.x
6.5 MEDIUM
AV:N/AC:L/Au:S/C:P/I:P/A:P
RedHat/V2
RedHat/V3
Ubuntu
MEDIUM
root.io logo minimus.io logo echo.ai logo

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.

Weakness

The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.

Affected Software

NameVendorStart VersionEnd Version
SymfonySensiolabs2.8.0 (including)2.8.50 (excluding)
SymfonySensiolabs3.4.0 (including)3.4.26 (excluding)
SymfonySensiolabs4.1.0 (including)4.1.12 (excluding)
SymfonySensiolabs4.2.0 (including)4.2.7 (excluding)
SymfonyUbuntubionic*
SymfonyUbuntucosmic*
SymfonyUbuntudisco*
SymfonyUbuntuesm-apps/bionic*
SymfonyUbuntuupstream*

Potential Mitigations

  • Make fields transient to protect them from deserialization.
  • An attempt to serialize and then deserialize a class containing transient fields will result in NULLs where the transient data should be. This is an excellent way to prevent time, environment-based, or sensitive variables from being carried over and used improperly.

References