Skip to content

Symfony Path Disclosure

Moderate severity GitHub Reviewed Published May 14, 2022 to the GitHub Advisory Database • Updated Feb 6, 2024

Package

composer symfony/form (Composer)

Affected versions

>= 2.7.0, < 2.7.50
>= 2.8.0, < 2.8.49
>= 3.0.0, < 3.4.20
>= 4.0.0, < 4.0.15
>= 4.1.0, < 4.1.9
>= 4.2.0, < 4.2.1

Patched versions

2.7.50
2.8.49
3.4.20
4.0.15
4.1.9
4.2.1
composer symfony/symfony (Composer)
>= 2.7.0, < 2.7.50
>= 2.8.0, < 2.8.49
>= 3.0.0, < 3.4.20
>= 4.0.0, < 4.0.15
>= 4.1.0, < 4.1.9
>= 4.2.0, < 4.2.1
2.7.50
2.8.49
3.4.20
4.0.15
4.1.9
4.2.1

Description

An issue was discovered in Symfony 2.7.x before 2.7.50, 2.8.x before 2.8.49, 3.x before 3.4.20, 4.0.x before 4.0.15, 4.1.x before 4.1.9, and 4.2.x before 4.2.1. When using the scalar type hint string in a setter method (e.g. setName(string $name)) of a class that's the data_class of a form, and when a file upload is submitted to the corresponding field instead of a normal text input, then UploadedFile::__toString() is called which will then return and disclose the path of the uploaded file. If combined with a local file inclusion issue in certain circumstances this could escalate it to a Remote Code Execution.

References

Published by the National Vulnerability Database Dec 18, 2018
Published to the GitHub Advisory Database May 14, 2022
Reviewed Jul 24, 2023
Last updated Feb 6, 2024

Severity

Moderate

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
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:N/UI:N/S:U/C:L/I:N/A:N

EPSS score

0.772%
(82nd percentile)

Weaknesses

CVE ID

CVE-2018-19789

GHSA ID

GHSA-x3cf-w64x-4cp2

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.