Scanning-engine crash via malformed PE32 files
Published May 23, 2022 · Updated Aug 3, 2024
Heap-buffer overflows in F-Secure and WithSecure security products allow remote attackers to crash the scanning engine with PE32 files. The scanning engine corrupts memory and writes beyond heap-buffer boundaries while parsing malformed PE32 input. A crafted file must enter a protected scan path; the resulting process crash interrupts malware scanning, and the vendor reports no known exploitation.
Summary
What happened
Heap-buffer overflows in F-Secure and WithSecure security products allow remote attackers to crash the scanning engine with PE32 files. The scanning engine corrupts memory and writes beyond heap-buffer boundaries while parsing malformed PE32 input. A crafted file must enter a protected scan path; the resulting process crash interrupts malware scanning, and the vendor reports no known exploitation.
The record
- CVE
- CVE-2022-28874
- Published
- May 23, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499.004
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- May 23, 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.
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