SensioLabs Symfony 6.1.1

CPE Details

SensioLabs Symfony 6.1.1
6.1.1
2023-02-10
17h04 +00:00
2023-02-13
16h23 +00:00
Alerte pour un CPE
Stay informed of any changes for a specific CPE.
Notifications manage

CPE Name: cpe:2.3:a:sensiolabs:symfony:6.1.1:*:*:*:*:*:*:*

Informations

Vendor

sensiolabs

Product

symfony

Version

6.1.1

Related CVE

Open and find in CVE List

CVE ID Published Description Score Severity
CVE-2023-46735 2023-11-10 17h58 +00:00 Symfony is a PHP framework for web and console applications and a set of reusable PHP components. Starting in version 6.0.0 and prior to version 6.3.8, the error message in `WebhookController` returns unescaped user-submitted input. As of version 6.3.8, `WebhookController` now doesn't return any user-submitted input in its response.
6.1
Medium
CVE-2023-46734 2023-11-10 17h49 +00:00 Symfony is a PHP framework for web and console applications and a set of reusable PHP components. Starting in versions 2.0.0, 5.0.0, and 6.0.0 and prior to versions 4.4.51, 5.4.31, and 6.3.8, some Twig filters in CodeExtension use `is_safe=html` but don't actually ensure their input is safe. As of versions 4.4.51, 5.4.31, and 6.3.8, Symfony now escapes the output of the affected filters.
6.1
Medium
CVE-2022-24894 2023-02-03 21h46 +00:00 Symfony is a PHP framework for web and console applications and a set of reusable PHP components. The Symfony HTTP cache system, acts as a reverse proxy: It caches entire responses (including headers) and returns them to the clients. In a recent change in the `AbstractSessionListener`, the response might contain a `Set-Cookie` header. If the Symfony HTTP cache system is enabled, this response might bill stored and return to the next clients. An attacker can use this vulnerability to retrieve the victim's session. This issue has been patched and is available for branch 4.4.
8.8
High
CVE-2022-24895 2023-02-03 21h45 +00:00 Symfony is a PHP framework for web and console applications and a set of reusable PHP components. When authenticating users Symfony by default regenerates the session ID upon login, but preserves the rest of session attributes. Because this does not clear CSRF tokens upon login, this might enables same-site attackers to bypass the CSRF protection mechanism by performing an attack similar to a session-fixation. This issue has been fixed in the 4.4 branch.
8.8
High