Symfony up to 2.8.50/3.4.34/4.2.11/4.3.7 UriSigner race condition

Summaryinfo

A vulnerability, which was classified as critical, has been found in Symfony up to 2.8.50/3.4.34/4.2.11/4.3.7. This affects an unknown function of the component UriSigner. This manipulation causes race condition. This vulnerability is tracked as CVE-2019-18887. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in Symfony up to 2.8.50/3.4.34/4.2.11/4.3.7. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the component UriSigner. The manipulation with an unknown input leads to a race condition vulnerability. The CWE definition for the vulnerability is CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

An issue was discovered in Symfony 2.8.0 through 2.8.50, 3.4.0 through 3.4.34, 4.2.0 through 4.2.11, and 4.3.0 through 4.3.7. The UriSigner was subject to timing attacks. This is related to symfony/http-kernel.

The weakness was disclosed 11/21/2019 (Website). The advisory is shared at lists.fedoraproject.org. This vulnerability is known as CVE-2019-18887 since 11/12/2019. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The entries VDB-146078 and VDB-146079 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• Symfony

Version

• 2.8.0
• 2.8.1
• 2.8.2
• 2.8.3
• 2.8.4
• 2.8.5
• 2.8.6
• 2.8.7
• 2.8.8
• 2.8.9
• 2.8.10
• 2.8.11
• 2.8.12
• 2.8.13
• 2.8.14
• 2.8.15
• 2.8.16
• 2.8.17
• 2.8.18
• 2.8.19
• 2.8.20
• 2.8.21
• 2.8.22
• 2.8.23
• 2.8.24
• 2.8.25
• 2.8.26
• 2.8.27
• 2.8.28
• 2.8.29
• 2.8.30
• 2.8.31
• 2.8.32
• 2.8.33
• 2.8.34
• 2.8.35
• 2.8.36
• 2.8.37
• 2.8.38
• 2.8.39
• 2.8.40
• 2.8.41
• 2.8.42
• 2.8.43
• 2.8.44
• 2.8.45
• 2.8.46
• 2.8.47
• 2.8.48
• 2.8.49
• 2.8.50
• 3.4.0
• 3.4.1
• 3.4.2
• 3.4.3
• 3.4.4
• 3.4.5
• 3.4.6
• 3.4.7
• 3.4.8
• 3.4.9
• 3.4.10
• 3.4.11
• 3.4.12
• 3.4.13
• 3.4.14
• 3.4.15
• 3.4.16
• 3.4.17
• 3.4.18
• 3.4.19
• 3.4.20
• 3.4.21
• 3.4.22
• 3.4.23
• 3.4.24
• 3.4.25
• 3.4.26
• 3.4.27
• 3.4.28
• 3.4.29
• 3.4.30
• 3.4.31
• 3.4.32
• 3.4.33
• 3.4.34
• 4.2.0
• 4.2.1
• 4.2.2
• 4.2.3
• 4.2.4
• 4.2.5
• 4.2.6
• 4.2.7
• 4.2.8
• 4.2.9
• 4.2.10
• 4.2.11
• 4.3.0
• 4.3.1
• 4.3.2
• 4.3.3
• 4.3.4
• 4.3.5
• 4.3.6
• 4.3.7

License

• open-source

Website

• Product: https://github.com/symfony/symfony/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion