Unauthenticated code execution via unsafe token deserialization
Published May 12, 2022 · Updated Aug 3, 2024
Deserialization in PHPOK 6.1 allows remote attackers to execute arbitrary code through a crafted quickcode value sent to update_f(). The administrative login controller passes decoded attacker-controlled content to unserialize(), enabling a cache-object destructor to write an executable PHP file. The exposed login endpoint requires no prior authentication, and successful exploitation runs code with the web server process's access.
Summary
What happened
Deserialization in PHPOK 6.1 allows remote attackers to execute arbitrary code through a crafted quickcode value sent to update_f(). The administrative login controller passes decoded attacker-controlled content to unserialize(), enabling a cache-object destructor to write an executable PHP file. The exposed login endpoint requires no prior authentication, and successful exploitation runs code with the web server process's access.
The record
- CVE
- CVE-2022-29363
- Published
- May 12, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-502, T1190, T1505.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 12, 2022CVE 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?
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
- PHPOK 6.1 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