GHSA-pfg4-p438-p874 json
Laravel Framework Deserialization Vulnerability
published 4y ago modified 2y ago also CVE-2019-9081
- cvss
- 9.8
- version 3.0, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
The Illuminate component of Laravel Framework 5.7.x has a deserialization vulnerability that can lead to remote code execution if the content is controllable, related to the `__destruct` method of the PendingCommand class in `PendingCommand.php`.
Patch / fix
- packagist laravel/framework 6.20.44
Is GHSA-pfg4-p438-p874 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 FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | laravel/framework | >=5.7.0, <6.20.44 |
6.20.44 |
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
References
-
nvd.nist.gov
/vuln/detail/CVE-2019-9081
advisory
-
github.com
/Laworigin/Laworigin.github.io/blob/master/2019/02/21/laravelv5-7%E5%8F%8D%E5%BA%8F%E5%88%97%E5%8C%96rce/index
web
-
github.com
/laravel/framework
package
-
github.com
/laravel/framework/discussions/40184
web
-
laworigin.github.io
/2019/02/21/laravelv5-7%E5%8F%8D%E5%BA%8F%E5%88%97%E5%8C%96rce
web
Sources
- GitHub Advisory GHSA-pfg4-p438-p874
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.