Authenticated code execution via unvalidated module upload
Published Mar 29, 2022 · Updated Aug 2, 2024
Insecure deserialization in Crater before 6.0.6 allows remote authenticated users with module-management rights to execute server code. The module upload and unzip controllers passed an uploaded ZIP, module name, and extraction path to ModuleInstaller without validating file type, size, or path syntax before module data was deserialized. Administrative manage-modules permission is required; successful exploitation grants control over the application server and its accessible data.
Summary
What happened
Insecure deserialization in Crater before 6.0.6 allows remote authenticated users with module-management rights to execute server code. The module upload and unzip controllers passed an uploaded ZIP, module name, and extraction path to ModuleInstaller without validating file type, size, or path syntax before module data was deserialized. Administrative manage-modules permission is required; successful exploitation grants control over the application server and its accessible data.
The record
- CVE
- CVE-2022-1032
- Published
- Mar 29, 2022
- Updated
- Aug 2, 2024
- Vendor
- Crater Invoice, Inc.
- Product
- Crater
- Classifications
- CWE-502, T1190
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Mar 29, 2022CVE publishedPublication date reported by the CVE source.
- Aug 2, 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=unspecified <6.0.6
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