GHSA-7852-w36x-6mf6 json
Laravel Encrypter Component Potential Decryption Failure Leading to Unintended Behavior
published 2y ago modified last yr.
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
The Laravel Encrypter component is susceptible to a vulnerability that may result in decryption failure, leading to an unexpected return of `false`. Exploiting this issue requires the attacker to manipulate the encrypted payload before decryption. When combined with weak type comparisons in the application's code, such as the example below:
``` <?php
$decyptedValue = decrypt($secret);
if ($decryptedValue == '') { // Code is run even though decrypted value is false... } ```
Patch / fix
- packagist laravel/framework 5.5.40, 5.6.15
Is GHSA-7852-w36x-6mf6 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | laravel/framework | <5.5.40 >=5.6.0, <5.6.15 |
5.5.40 5.6.15 |
Classification
- Weakness
-
- CWE-1240 Use of a Cryptographic Primitive with a Risky Implementation
References
-
github.com
/laravel/framework/commit/28e53f23a76206fb130e9a54eb95aa3f010e79c9
web
-
github.com
/laravel/framework/commit/886d261df0854426b4662b7ed5db6a1c575a4279
web
-
github.com
/FriendsOfPHP/security-advisories/blob/master/laravel/framework/2018-03-30-1.yaml
web
-
github.com
/laravel/framework
package
-
medium.com
/@taylorotwell/laravel-security-release-5-6-15-and-5-5-40-56f1257933a0
web
Sources
- GitHub Advisory GHSA-7852-w36x-6mf6
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.