Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Out-of-bounds Write in AzeoTech DAQFactory CTL File Parsing

IdentifiersCVE-2025-66590CWE-787· Out-of-bounds Write

CVE-2025-66590 is an out-of-bounds write vulnerability in AzeoTech DAQFactory release 20.7 (Build 2555), specifically in the parsing of CTL files. The flaw is caused by insufficient validation of user-supplied data during CTL file processing, allowing the application to write past the end of an allocated memory buffer. This memory corruption condition can be triggered by a crafted malicious CTL file and may result in arbitrary code execution in the context of the current process or application instability/crash.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can corrupt process memory, causing the application to crash or enabling arbitrary code execution in the context of the current DAQFactory process. Because the vulnerable software is used in ICS environments, compromise could affect the confidentiality, integrity, and availability of the host running DAQFactory.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure to malicious CTL files by restricting who can create, modify, upload, or open CTL files; use DAQFactory safe mode where applicable; apply document editing/password protections mentioned by the vendor/CISA guidance; and follow ICS hardening practices such as minimizing network exposure, isolating control-system assets, placing systems behind firewalls, and securing remote access through VPNs. User awareness controls to prevent opening untrusted project files also reduce risk.

Remediation

Patch, then assume compromise.

Update AzeoTech DAQFactory to a vendor-fixed release. The provided content indicates that AzeoTech issued an update to correct the vulnerability and that DAQFactory version 21.1 addresses this issue. Apply the latest vendor-supplied security patches and validate the update in a test environment before deployment.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
AzeotechDaqfactoryapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity1

Community discussion across Reddit, Mastodon, and other social sources.