HighGHSA-rcgc-4xfc-564vCVE-2019-19849

TYPO3 Insecure Deserialization in Query Generator & Query View

Published 24 May 2022 · Updated 25 Apr 2024

Affected packages

Affected
>=10.0.0 <10.2.1
Fixed in
10.2.1
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^10.2.1
Affected
>=8.0.0 <8.7.30
Fixed in
8.7.30
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^8.7.30
Affected
>=9.0.0 <9.5.12
Fixed in
9.5.12
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^9.5.12
typo3/cmsComposer
Affected
>=10.0.0 <10.2.1
Fixed in
10.2.1
Update to the fixed version for your release line, for example:composer require typo3/cms:^10.2.1
typo3/cmsComposer
Affected
>=8.0.0 <8.7.30
Fixed in
8.7.30
Update to the fixed version for your release line, for example:composer require typo3/cms:^8.7.30
typo3/cmsComposer
Affected
>=9.0.0 <9.5.12
Fixed in
9.5.12
Update to the fixed version for your release line, for example:composer require typo3/cms:^9.5.12

Details

An issue was discovered in TYPO3 before 8.7.30, 9.x before 9.5.12, and 10.x before 10.2.2. It has been discovered that the classes QueryGenerator and QueryView are vulnerable to insecure deserialization. One exploitable scenario requires having the system extension ext:lowlevel (Backend Module: DB Check) installed, with a valid backend user who has administrator privileges. The other exploitable scenario requires having the system extension ext:sys_action installed, with a valid backend user who has limited privileges.

Is GHSA-rcgc-4xfc-564v in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected typo3/cms-core, and gives you the command that fixes it.

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.