Memory corruption via unsafe project-file deserialization
Published Nov 5, 2021 · Updated Aug 4, 2024
Unsafe deserialization in AzeoTech DAQFactory 18.1 Build 2347 and earlier allows attackers to corrupt memory through a crafted project file. The project-file loader reconstructs in-memory objects from binary serialized data without safely rejecting maliciously altered object data. Exploitation requires a victim to open the file locally, and the published impact is memory corruption rather than a demonstrated code-execution path.
Summary
What happened
Unsafe deserialization in AzeoTech DAQFactory 18.1 Build 2347 and earlier allows attackers to corrupt memory through a crafted project file. The project-file loader reconstructs in-memory objects from binary serialized data without safely rejecting maliciously altered object data. Exploitation requires a victim to open the file locally, and the published impact is memory corruption rather than a demonstrated code-execution path.
The record
- CVE
- CVE-2021-42698
- Published
- Nov 5, 2021
- Updated
- Aug 4, 2024
- Vendor
- AzeoTech
- Product
- DAQFactory
- Classifications
- CWE-502, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 5, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=All versions <=New version
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.
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