Authenticated code execution via crafted filename value
Published Feb 10, 2022 · Updated Aug 4, 2024
Code injection in ThinkPHP 3.2.3 and earlier allows remote authenticated users to execute arbitrary code via value[_filename] in index.php. The public CNA and reviewed GitHub records identify that request parameter and file as the vulnerable locus but do not disclose the operation that turns the supplied filename value into code execution. Low-privileged network access is required, and successful exploitation grants control of the server process and its accessible data.
Summary
What happened
Code injection in ThinkPHP 3.2.3 and earlier allows remote authenticated users to execute arbitrary code via value[_filename] in index.php. The public CNA and reviewed GitHub records identify that request parameter and file as the vulnerable locus but do not disclose the operation that turns the supplied filename value into code execution. Low-privileged network access is required, and successful exploitation grants control of the server process and its accessible data.
The record
- CVE
- CVE-2021-44892
- Published
- Feb 10, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 10, 2022CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo