-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
Security Vulnerability - Cross-site Scripting #27987
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Please note that Symfony 3.0 does not receive any security updates anymore. But if you think that Symfony 2.8 is still affected by the bug, please open a PR in this repository. Please also note to report security issues in the future via e-mail to security (at) symfony.com. In this case, that's not a big deal as the web debug toolbar should never be accessible to the users of your website. |
This bug was fixed a long time ago on all supported versions of Symfony. See #23684 |
details: symfony#27987
CVE-2017-18343 was assigned to this issue. |
Uh oh!
There was an error while loading. Please reload this page.
Symfony Debug version(s) affected: 2.8.*|3.0.*
Injection Technical Details
URL: http://{domain}/{laravel_path}/_debugbar/open?op=get&id=om3rcitak&<scRipt>alert(21)<%2fscRipt>=om3rcitak
Parameter Type: Parameter Name
Attack Pattern: <scRipt>alert(21)<%2fscRipt>
Repro
$
composer create-project --prefer-dist laravel/laravel:5.2.*
$
cd laravel
$
composer require barryvdh/laravel-debugbar:~2.4
$
php artisan vendor:publish --provider="Barryvdh\Debugbar\ServiceProvider"
$
php artisan serve
and visit: http://{domain}/{laravel_path}/_debugbar/open?op=get&id=om3rcitak&<scRipt>alert(21)<%2fscRipt>=om3rcitak
Possible Solution
Actually your fix this vulnerability 4.* version but laravel 5.2.* using symfony/debug 2.8.|3.0.. Your should be same fix for 2.8.|3.0. versions.
I send pull-request for fix this vulnerability: symfony/debug@e48bda2
Notes: I am testing laravel-debugger latest version (2.4) for Laravel 5.2.*. This vulnerability not effected Laravel >= 5.3 or laravel-debugger >=3.0 because Laravel using different error page template for version 5.2 and 5.3.
The text was updated successfully, but these errors were encountered: