Symfony up to 4.0-BETA4 CSRF Protection 7pk security

Summaryinfo

A vulnerability marked as problematic has been reported in Symfony up to 4.0-BETA4. Affected by this issue is some unknown functionality of the component CSRF protection. The manipulation leads to 7pk security. This vulnerability is documented as CVE-2017-16653. The attack can be initiated remotely. There is not any exploit available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in Symfony up to 4.0-BETA4. It has been rated as problematic. This issue affects an unknown code of the component CSRF Protection. The manipulation with an unknown input leads to a 7pk security vulnerability. Using CWE to declare the problem leads to CWE-254. Impacted is integrity. The summary by CVE is:

An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.

The bug was discovered 11/17/2017. The weakness was released 08/06/2018 (Website). It is possible to read the advisory at debian.org. The identification of this vulnerability is CVE-2017-16653 since 11/06/2017. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1211 according to MITRE ATT&CK.

The vulnerability was handled as a non-public zero-day exploit for at least 259 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 111535 (Debian DSA-4262-1 : symfony - security update), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Debian Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 176446 (Debian Security Update for symfony (DSA 4262-1)).

Upgrading to version 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5 or 4.0-BETA5 eliminates this vulnerability. A possible mitigation has been published even before and not after the disclosure of the vulnerability.

The vulnerability is also documented in the vulnerability database at Tenable (111535). Entries connected to this vulnerability are available at VDB-96595, VDB-111332, VDB-119502 and VDB-119503. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• Symfony

Version

• 2.7.0
• 2.7.1
• 2.7.2
• 2.7.3
• 2.7.4
• 2.7.5
• 2.7.6
• 2.7.7
• 2.7.8
• 2.7.9
• 2.7.10
• 2.7.11
• 2.7.12
• 2.7.13
• 2.7.14
• 2.7.15
• 2.7.16
• 2.7.17
• 2.7.18
• 2.7.19
• 2.7.20
• 2.7.21
• 2.7.22
• 2.7.23
• 2.7.24
• 2.7.25
• 2.7.26
• 2.7.27
• 2.7.28
• 2.7.29
• 2.7.30
• 2.7.31
• 2.7.32
• 2.7.33
• 2.7.34
• 2.7.35
• 2.7.36
• 2.7.37
• 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
• 3.2.0
• 3.2.1
• 3.2.2
• 3.2.3
• 3.2.4
• 3.2.5
• 3.2.6
• 3.2.7
• 3.2.8
• 3.2.9
• 3.2.10
• 3.2.11
• 3.2.12
• 3.2.13
• 3.3.0
• 3.3.1
• 3.3.2
• 3.3.3
• 3.3.4
• 3.3.5
• 3.3.6
• 3.3.7
• 3.3.8
• 3.3.9
• 3.3.10
• 3.3.11
• 3.3.12
• 3.4-BETA4
• 4.0-BETA4

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

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion