Malicious package verification via colliding key identifiers
Published Jul 28, 2025 · Updated Nov 4, 2025
Signature verification bypass in HP Linux Imaging and Printing before 3.25.2 allows attackers to authenticate malicious packages. HP's manual-installation documentation requests the signing key by a collision-prone 32-bit key ID, so GPG can import an attacker-controlled key and accept its signatures. The attack requires a user to obtain a malicious package outside a native package manager and follow the documented manual verification workflow before execution.
Summary
What happened
Signature verification bypass in HP Linux Imaging and Printing before 3.25.2 allows attackers to authenticate malicious packages. HP's manual-installation documentation requests the signing key by a collision-prone 32-bit key ID, so GPG can import an attacker-controlled key and accept its signatures. The attack requires a user to obtain a malicious package outside a native package manager and follow the documented manual verification workflow before execution.
The record
- CVE
- CVE-2025-43023
- Published
- Jul 28, 2025
- Updated
- Nov 4, 2025
- Vendor
- Plantronics
- Product
- HP Linux Imaging and Printing (HPLIP)
- Classifications
- CWE-347, T1553
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Jul 28, 2025CVE publishedPublication date reported by the CVE source.
- Nov 4, 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
- HPLIP short-key-identifier spoofing demonstrationproof 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