Security Fixes

The 3.10.3 release contains an opt in security fix for CsrfProtectionMiddleware. Prior to this release, if an application has a cross-site-scripting vulnerability, or an attacker has access to a victim’s browser CSRF tokens could be manipulated allowing CSRF bypass. This weakness stems from CSRF middleware accepting any matching pair of tokens. With the fix applied, only tokens generated by the host application will be accepted. This fix requires opt-in because it breaks compatibility with existing CSRF tokens that may be in user’s browsers/sessions. To enable the new style tokens add the following:

// in src/Application.php
$middlewareQueue->add(new CsrfProtectionMiddleware([
    'verifyTokenSource' => true
]));

Bugfixes

You can expect the following changes in 3.10.3. See the changelog for every commit.

• Fixed a memory leak in TranslatorRegistry when loading translations from cache.

Contributors to 3.10.3

Thank you to all the contributors that helped make this release happen:

• Mark Story
• Val Bancer

As always, we would like to thank all the contributors that opened issues, created pull requests or updated the documentation.

Download a packaged release on github.