Remote code execution via Unicode whitespace stripping
Published Jun 24, 2021 · Updated Aug 3, 2024
Path normalization in The PHP League Flysystem before 1.1.4 and 2.0.0 through 2.1.0 allows remote attackers to execute PHP code. WhitespacePathNormalizer removes Unicode control characters from an attacker-supplied path, allowing a denied extension containing such a character to become executable after validation. Exploitation requires control of an uploaded path or filename, extension deny-list validation without prior Unicode rejection, and storage in a PHP-executable directory.
Summary
What happened
Path normalization in The PHP League Flysystem before 1.1.4 and 2.0.0 through 2.1.0 allows remote attackers to execute PHP code. WhitespacePathNormalizer removes Unicode control characters from an attacker-supplied path, allowing a denied extension containing such a character to become executable after validation. Exploitation requires control of an uploaded path or filename, extension deny-list validation without prior Unicode rejection, and storage in a PHP-executable directory.
The record
- CVE
- CVE-2021-32708
- Published
- Jun 24, 2021
- Updated
- Aug 3, 2024
- Vendor
- The PHP League
- Product
- Flysystem
- Classifications
- CWE-367, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 24, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.1.4
- Affected versionversion=>= 2.0.0, < 2.1.1
What conditions does exploitation require?
What is affected?
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