dbcve.org
DaqfactoryApplication · Azeotech

CVE-2025-66586

HIGH · 7.8 CVSS v3.1 Published 2025-12-11
Fix available
A fix is available. Upgrade to 21.1 or later.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In AzeoTech DAQFactory release 20.7 (Build 2555), an access of resource using incompatible type vulnerability can be exploited to cause memory corruption while parsing specially crafted .ctl files. This could allow an attacker to execute code in the context of the current process.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

AzeoTech DAQFactory 20.7 (Build 2555) contains a type confusion vulnerability during .ctl file parsing that leads to memory corruption. An attacker can exploit this by crafting a malicious .ctl file to achieve arbitrary code execution within the context of the running process.

MitigationApply the vendor patch when available. Until then, restrict access to .ctl files from untrusted sources and disable file import features if possible. Network segmentation can limit exposure if this software is exposed externally.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DaqfactoryApplication
Affected:< 21.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed DAQFactory version
    Locate the DAQFactory installation directory and check the version information (typically in the main executable properties or in the About dialog within the application). Compare the version number to the affected range of versions prior to 21.1.
    Affected if The installed version is earlier than 21.1 (for example, version 20.7 or any earlier release).
  2. Determine if .ctl file import is enabled
    Check whether the file import or file open functionality for .ctl files is active in the DAQFactory environment. This may be configured in the application settings, startup scripts, or automation configurations that handle .ctl file loading.
    Affected if The .ctl file import or parsing feature is enabled and accessible.
  3. Locate .ctl files in the environment
    Search the system for .ctl files, particularly in directories where DAQFactory projects, scripts, or data files are stored. Review any automated import paths configured in DAQFactory.
    Affected if There are .ctl files present that could be parsed by DAQFactory, especially from untrusted sources.
  4. Assess network exposure of DAQFactory
    Determine whether DAQFactory is accessible over the network or accepts files from remote/untrusted sources. Check firewall rules and service configurations that may allow external entities to supply .ctl files to the application.
    Affected if DAQFactory is exposed to network access or can receive files from untrusted sources without validation.

A system is affected if it runs Azeotech DAQFactory version earlier than 21.1 with .ctl file parsing functionality enabled and accessible to potential malicious .ctl files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 21.1 or later
Fixed in 21.1
Interim mitigation

Apply the vendor patch when available. Until then, restrict access to .ctl files from untrusted sources and disable file import features if possible. Network segmentation can limit exposure if this software is exposed externally.

Recommended fix High confidence

DAQFactory 21.1 or later

  1. 1. Backup all existing .ctl files, project files, and DAQFactory configuration data before proceeding.
  2. 2. Obtain DAQFactory version 21.1 or later from the official AzeoTech vendor (azeotech.com or through their official distribution channels).
  3. 3. Uninstall the current DAQFactory version (20.7 or earlier).
  4. 4. Install the fixed version 21.1 following standard installation procedures.
  5. 5. After installation, restore backed-up .ctl files and project configurations.
  6. 6. Test critical .ctl file parsing operations to verify the vulnerability is resolved and functionality is intact.
Caveat Review release notes for version 21.1 to check for any breaking changes in .ctl file format or scripting features that may affect existing projects

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Daqfactory Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-66586 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-66586 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data