GHSA-wq43-8r5p-w3mc json
contao/core PHP object injection vulnerability allows for arbitrary code execution
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
PHP object injection vulnerability was identified in contao/core due to untrusted data being passed to `deserialize()` function.
Patch / fix
- packagist contao/core 2.11.14, 3.2.5
- github.com/contao/core@d67c46c commit
- github.com/contao/core@f939b5b commit
Is GHSA-wq43-8r5p-w3mc 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 | contao/core | >=2.0.0, <2.11.14 >=3.0.0, <3.2.5 |
2.11.14 3.2.5 |
References
-
github.com
/contao/core/commit/d67c46c1f1283134e3050244cfdda0ef26fa5cd4
web
-
github.com
/contao/core/commit/f939b5be8a0048ef779def3289e2072febef1b37
web
-
github.com
/contao/core/issues/6695
web
-
contao.org
/en/news/major-security-hole-found-in-contao.html
web
-
github.com
/FriendsOfPHP/security-advisories/blob/master/contao/core/2014-02-13.yaml
web
Sources
- GitHub Advisory GHSA-wq43-8r5p-w3mc
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.