Arbitrary code execution via modified configuration file
Published May 1, 2024 · Updated Mar 27, 2025
Code injection in HP Software Packages (SoftPaqs) allows local users to execute arbitrary code through a modified post-extraction configuration file. HP has not disclosed which configuration field or package-processing routine accepts the altered value, or how that value reaches code execution. Exploitation requires local access, high privileges, and user interaction; successful execution can cross a security boundary and affect confidentiality, integrity, and availability.
Summary
What happened
Code injection in HP Software Packages (SoftPaqs) allows local users to execute arbitrary code through a modified post-extraction configuration file. HP has not disclosed which configuration field or package-processing routine accepts the altered value, or how that value reaches code execution. Exploitation requires local access, high privileges, and user interaction; successful execution can cross a security boundary and affect confidentiality, integrity, and availability.
The record
- CVE
- CVE-2024-28893
- Published
- May 1, 2024
- Updated
- Mar 27, 2025
- Vendor
- Plantronics
- Product
- HP Software Packages (SoftPaqs)
- Classifications
- CWE-94, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- May 1, 2024CVE publishedPublication date reported by the CVE source.
- Mar 27, 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=-
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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