Skip to content

Deserialization of untrusted data in Symfony

High severity GitHub Reviewed Published Feb 12, 2020 to the GitHub Advisory Database • Updated Feb 5, 2024

Package

composer symfony/cache (Composer)

Affected versions

>= 3.1.0, < 3.4.26
>= 4.0.0, < 4.1.12
>= 4.2.0, < 4.2.7

Patched versions

3.4.26
4.1.12
4.2.7
composer symfony/phpunit-bridge (Composer)
>= 2.8.0, < 2.8.50
>= 3.0.0, < 3.4.26
>= 4.0.0, < 4.1.12
>= 4.2.0, < 4.2.7
2.8.50
3.4.26
4.1.12
4.2.7
composer symfony/symfony (Composer)
>= 2.8.0, < 2.8.50
>= 3.0.0, < 3.4.26
>= 4.0.0, < 4.1.12
>= 4.2.0, < 4.2.7
2.8.50
3.4.26
4.1.12
4.2.7
composer typo3/cms (Composer)
>= 9.0.0, < 9.5.8
9.5.8
composer typo3/cms-core (Composer)
>= 9.0.0, < 9.5.8
9.5.8

Description

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.

References

Published by the National Vulnerability Database May 16, 2019
Reviewed Feb 11, 2020
Published to the GitHub Advisory Database Feb 12, 2020
Last updated Feb 5, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N

EPSS score

0.359%
(73rd percentile)

Weaknesses

CVE ID

CVE-2019-10912

GHSA ID

GHSA-w2fr-65vp-mxw3

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.