Skip to content

TYPO3 Insecure Deserialization in Query Generator & Query View

High severity GitHub Reviewed Published May 24, 2022 to the GitHub Advisory Database • Updated Apr 25, 2024

Package

composer typo3/cms (Composer)

Affected versions

>= 10.0.0, < 10.2.1
>= 8.0.0, < 8.7.30
>= 9.0.0, < 9.5.12

Patched versions

10.2.1
8.7.30
9.5.12
composer typo3/cms-core (Composer)
>= 10.0.0, < 10.2.1
>= 8.0.0, < 8.7.30
>= 9.0.0, < 9.5.12
10.2.1
8.7.30
9.5.12

Description

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.

References

Published by the National Vulnerability Database Dec 17, 2019
Published to the GitHub Advisory Database May 24, 2022
Reviewed Apr 25, 2024
Last updated Apr 25, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.102%
(43rd percentile)

Weaknesses

CVE ID

CVE-2019-19849

GHSA ID

GHSA-rcgc-4xfc-564v

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.