Remote code execution via case-insensitive PHAR bypass
Published Sep 6, 2023 · Updated Sep 30, 2024
Unsafe PHAR deserialization in KNP Labs Snappy before 1.4.3 allows remote attackers to execute arbitrary code via a crafted output filename. The prepareOutput function checks only lowercase phar:// before fileExists processes the filename, although PHP wrapper schemes are case-insensitive. Exploitation requires control of the output filename, upload of a crafted PHAR file, and PHP 7 or earlier; success grants code execution and filesystem access.
Summary
What happened
Unsafe PHAR deserialization in KNP Labs Snappy before 1.4.3 allows remote attackers to execute arbitrary code via a crafted output filename. The prepareOutput function checks only lowercase phar:// before fileExists processes the filename, although PHP wrapper schemes are case-insensitive. Exploitation requires control of the output filename, upload of a crafted PHAR file, and PHP 7 or earlier; success grants code execution and filesystem access.
The record
- CVE
- CVE-2023-41330
- Published
- Sep 6, 2023
- Updated
- Sep 30, 2024
- Vendor
- KNP Labs
- Product
- Snappy
- Classifications
- CWE-502, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 6, 2023CVE publishedPublication date reported by the CVE source.
- Sep 30, 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.4.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- GitHub advisory PHAR deserialization proof of conceptproof of concept · demonstrated
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