Skip to content

Deserialization of Untrusted Data in topthink/framework

Critical severity GitHub Reviewed Published Dec 10, 2021 to the GitHub Advisory Database • Updated Sep 19, 2023

Package

composer topthink/framework (Composer)

Affected versions

< 6.0.9

Patched versions

6.0.9

Description

ThinkPHP v6.0.8 was discovered to contain a deserialization vulnerability via the component vendor\league\flysystem-cached-adapter\src\Storage\Adapter.php.

References

Published by the National Vulnerability Database Dec 6, 2021
Reviewed Dec 8, 2021
Published to the GitHub Advisory Database Dec 10, 2021
Last updated Sep 19, 2023

Severity

Critical

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
None
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.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.842%
(82nd percentile)

Weaknesses

CVE ID

CVE-2021-36564

GHSA ID

GHSA-33gc-6cw9-w3g4

Source code

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