Disputed code execution via application-controlled upload paths
Published May 16, 2022 · Updated Aug 3, 2024
The disputed arbitrary file upload claim in formidable 3.1.4 states remote attackers can execute code via a crafted filename. The reported locus is originalFilename: the multipart parser returns the client-supplied name to consuming code rather than enforcing a safe storage name. Exploitation requires application code to store and execute an uploaded file by that name; upstream users dispute that this intended library behavior constitutes a vulnerability, and GitHub withdrew its advisory as improperly assigned.
Summary
What happened
The disputed arbitrary file upload claim in formidable 3.1.4 states remote attackers can execute code via a crafted filename. The reported locus is originalFilename: the multipart parser returns the client-supplied name to consuming code rather than enforcing a safe storage name. Exploitation requires application code to store and execute an uploaded file by that name; upstream users dispute that this intended library behavior constitutes a vulnerability, and GitHub withdrew its advisory as improperly assigned.
The record
- CVE
- CVE-2022-29622
- Published
- May 16, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-434, CAPEC-1, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 16, 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
- Filename filtering reproductionproof 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