Authenticated injection via incompletely sanitized image filenames
Published Feb 18, 2022 · Updated Aug 3, 2024
Filename injection in Ibexa DXP 3.3 and eZ Platform 2.5 allows remote authenticated users to cause unspecified impact via image filenames. The image upload path uses the original filename to derive a public image name but fails to remove every injection vector during sanitization. Exploitation requires permission to upload images; Ibexa has not disclosed the injection sink or the resulting code-level consequence.
Summary
What happened
Filename injection in Ibexa DXP 3.3 and eZ Platform 2.5 allows remote authenticated users to cause unspecified impact via image filenames. The image upload path uses the original filename to derive a public image name but fails to remove every injection vector during sanitization. Exploitation requires permission to upload images; Ibexa has not disclosed the injection sink or the resulting code-level consequence.
The record
- CVE
- CVE-2022-25337
- Published
- Feb 18, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-74, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 18, 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
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