Authenticated dangerous-file upload via unchecked file type
Published Jan 12, 2025 · Updated Jan 13, 2025
Unrestricted file upload in reggie 1.0 allows remote authenticated users to place dangerous files through the CommonController upload endpoint. The upload function accepts the multipart file argument and stores it without enforcing an allowed file type. Valid application credentials are required, and the bounded result is storage of an attacker-chosen dangerous file; code execution is not established.
Summary
What happened
Unrestricted file upload in reggie 1.0 allows remote authenticated users to place dangerous files through the CommonController upload endpoint. The upload function accepts the multipart file argument and stores it without enforcing an allowed file type. Valid application credentials are required, and the bounded result is storage of an attacker-chosen dangerous file; code execution is not established.
The record
- CVE
- CVE-2025-0402
- Published
- Jan 12, 2025
- Updated
- Jan 13, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-434, CWE-284, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 12, 2025CVE publishedPublication date reported by the CVE source.
- Jan 13, 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?
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
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