Authenticated code execution via unsanitized file upload
Published Aug 6, 2024 · Updated Mar 19, 2025
Arbitrary file upload in HP Poly Clariti Manager firmware through 10.10.2.2 allows remote authenticated users to execute code. The firmware's upload handling does not properly sanitize user-supplied files, permitting a dangerous file type to be stored; HP has not disclosed the affected endpoint or validation logic. Low-privileged access to the network-facing management interface is required, and exploitation can alter data and interrupt service without reported confidentiality impact.
Summary
What happened
Arbitrary file upload in HP Poly Clariti Manager firmware through 10.10.2.2 allows remote authenticated users to execute code. The firmware's upload handling does not properly sanitize user-supplied files, permitting a dangerous file type to be stored; HP has not disclosed the affected endpoint or validation logic. Low-privileged access to the network-facing management interface is required, and exploitation can alter data and interrupt service without reported confidentiality impact.
The record
- CVE
- CVE-2024-41913
- Published
- Aug 6, 2024
- Updated
- Mar 19, 2025
- Vendor
- Plantronics
- Product
- Poly Clariti Manager
- Classifications
- CWE-434, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 6, 2024CVE publishedPublication date reported by the CVE source.
- Mar 19, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=See HP Security Bulletin reference for affected versions.
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