GHSA-6wjw-qf87-fv5v json
Laravel Encrypter Failure to decryption vulnerability
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
A potential exploit of the Laravel Encrypter component that may cause the Encrypter to fail on decryption and unexpectedly return false.
To exploit this, the attacker must be able to modify the encrypted payload before it is decrypted. Depending on the code within your application, this could lead to unexpected behavior when combined with weak type comparisons, for example:
```php <?php
$decyptedValue = decrypt($secret);
if ($decryptedValue == '') { // Code is run even though decrypted value is false... } ```
Patch / fix
- packagist illuminate/encryption 5.5.40, 5.6.15
Is GHSA-6wjw-qf87-fv5v 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 | illuminate/encryption | >=5.5.0, <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
/illuminate/encryption/commit/51667a52bd7d135c6aa40a897656ffe9d3cd072d
web
-
github.com
/illuminate/encryption/commit/c80b1da6a0412bd74bd56dc80f6126f561631b05
web
-
github.com
/FriendsOfPHP/security-advisories/blob/master/illuminate/encryption/2018-03-30-1.yaml
web
-
github.com
/illuminate/encryption
package
-
medium.com
/@taylorotwell/laravel-security-release-5-6-15-and-5-5-40-56f1257933a0
web
Sources
- GitHub Advisory GHSA-6wjw-qf87-fv5v
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.