Unauthenticated code execution via LLMNR buffer overflow
Published Nov 22, 2022 · Updated Apr 25, 2025
Buffer overflow in HP Print and Digital Sending products allows remote attackers to execute code through LLMNR traffic. HP identifies LLMNR handling as the vulnerable locus but has not published the affected parser or the specific operation that crosses a buffer boundary. Unauthenticated network access to the link-local name-resolution service is sufficient; exploitation can execute code or interrupt the device.
Summary
What happened
Buffer overflow in HP Print and Digital Sending products allows remote attackers to execute code through LLMNR traffic. HP identifies LLMNR handling as the vulnerable locus but has not published the affected parser or the specific operation that crosses a buffer boundary. Unauthenticated network access to the link-local name-resolution service is sufficient; exploitation can execute code or interrupt the device.
The record
- CVE
- CVE-2021-3942
- Published
- Nov 22, 2022
- Updated
- Apr 25, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-119, T1210
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 22, 2022CVE publishedPublication date reported by the CVE source.
- Apr 25, 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