Remote code execution via PHAR output path
Published Mar 17, 2023 · Updated Feb 25, 2025
PHAR deserialization in KNP Labs Snappy before 1.4.2 allows remote attackers to execute code through a crafted output filename. AbstractGenerator::prepareOutput passes an attacker-controlled phar:// output path to file_exists(), causing PHP to deserialize archive metadata. Exploitation requires control of the output filename, an uploaded PHAR file, and a usable object-injection chain; successful exploitation executes code in the application context.
Summary
What happened
PHAR deserialization in KNP Labs Snappy before 1.4.2 allows remote attackers to execute code through a crafted output filename. AbstractGenerator::prepareOutput passes an attacker-controlled phar:// output path to file_exists(), causing PHP to deserialize archive metadata. Exploitation requires control of the output filename, an uploaded PHAR file, and a usable object-injection chain; successful exploitation executes code in the application context.
The record
- CVE
- CVE-2023-28115
- Published
- Mar 17, 2023
- Updated
- Feb 25, 2025
- Vendor
- KNP Labs
- Product
- Snappy
- Classifications
- CWE-502, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 17, 2023CVE publishedPublication date reported by the CVE source.
- Feb 25, 2025Record 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.2
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
- GHSA-gq6w-q6wh-jggc 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