CVE-2022-2886 json
Laravel deserialization
published 4y ago modified 4mo ago also BIT-laravel-2022-2886 , EUVD-2022-35117
- cvss
- 5.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 54%
- public exploits
- 0
- none known
Summary
A vulnerability, which was classified as critical, was found in Laravel 5.1. Affected is an unknown function. The manipulation leads to deserialization. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-206688.
Patch / fix
- bitnami laravel 5.1.47
Is CVE-2022-2886 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 FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.73% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/beicheng-maker/vulns/issues/3 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.0 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| OSV | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | laravel | >=5.1.0, <5.1.47 |
5.1.47 |
Affected products
- unspecified Laravel
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
References
-
github.com
/beicheng-maker/vulns/issues/3
exploit, issue-tracking, third-party-advisory, web
-
vuldb.com
/?id.206688
third-party-advisory, web
-
nvd.nist.gov
/vuln/detail/CVE-2022-2886
web
Sources
- CVE List CVE-2022-2886
- NVD CVE-2022-2886
- OSV BIT-laravel-2022-2886
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.