Symfony up to 2.7.32/2.8.25/3.2.12/3.3.5 Debug ExceptionHandler.php cross site scripting ⚔ [Disputed]

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Symfony up to 2.7.32/2.8.25/3.2.12/3.3.5. The impacted element is an unknown function of the file ExceptionHandler.php of the component Debug Handler. The manipulation leads to cross site scripting. This vulnerability is uniquely identified as CVE-2017-18343. The attack is possible to be carried out remotely. No exploit exists. The actual existence of this vulnerability is currently in question. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in Symfony up to 2.7.32/2.8.25/3.2.12/3.3.5. This issue affects an unknown functionality of the file ExceptionHandler.php of the component Debug Handler. The manipulation with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. Impacted is integrity. The summary by CVE is:

** DISPUTED ** The debug handler in Symfony before v2.7.33, 2.8.x before v2.8.26, 3.x before v3.2.13, and 3.3.x before v3.3.6 has XSS via an array key during exception pretty printing in ExceptionHandler.php, as demonstrated by a /_debugbar/open?op=get URI. NOTE: the vendor's position is that this is not a vulnerability because the debug tools are not intended for production use. NOTE: the Symfony Debug component is used by Laravel Debugbar.

The weakness was disclosed 07/20/2018 (Website). The advisory is shared at github.com. The identification of this vulnerability is CVE-2017-18343 since 07/19/2018. 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. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.

The real existence of this vulnerability is still doubted at the moment. By approaching the search of inurl:ExceptionHandler.php it is possible to find vulnerable targets with Google Hacking.

Upgrading to version 2.7.33, 2.8.26, 3.2.13 or 3.3.6 eliminates this vulnerability.

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

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.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
• 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.3.0
• 3.3.1
• 3.3.2
• 3.3.3
• 3.3.4
• 3.3.5

License

• open-source

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