dbcve.org
DaqfactoryApplication · Azeotech

CVE-2025-66588

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-11
Fix available
A fix is available. Upgrade to 21.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 uninitialized pointer vulnerability can be exploited by an attacker which can lead to arbitrary code execution.

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 an access of uninitialized pointer vulnerability that can be exploited for arbitrary code execution. The vulnerability stems from a memory corruption issue where a pointer is used before proper initialization, potentially allowing an attacker to control memory addresses and achieve remote code execution.

MitigationApply vendor-provided patch for DAQFactory 20.7 once released; until then, restrict network access to DAQFactory systems and isolate from untrusted networks given the critical severity and RCE capability.

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Confirm DAQFactory installation
    Look for Azeotech DAQFactory in the system programs list, check Program Files folders for 'DAQFactory' directory, or search for the executable (typically at C:\Program Files\Azeotech\DAQFactory\ or similar path).
    Affected if DAQFactory software is present on the system.
  2. Identify installed DAQFactory version
    Open DAQFactory and navigate to Help > About, or check the version in the Windows Programs and Features list, or right-click the DAQFactory executable and view Properties > Details for version information.
    Affected if Unable to determine version or version is below 21.1.
  3. Determine build number
    In DAQFactory, go to Help > About or check the executable properties to find the specific build number. The vulnerability affects Build 2555 and potentially earlier builds.
    Affected if Build number is 2555 or lower.
  4. Compare version to affected range
    Verify that the installed version is any release prior to version 21.1. The vendor advisory indicates versions below 21.1 are affected.
    Affected if Installed version is 20.7.x or any earlier version line.
  5. Assess network exposure
    Review Windows Firewall rules and network configuration to determine if DAQFactory service ports are open to untrusted networks. Check if the application listens on any network interfaces (0.0.0.0) rather than localhost only.
    Affected if DAQFactory is accessible from network hosts, especially untrusted networks.

The environment is affected if Azeotech DAQFactory version 20.7 (Build 2555) or any version below 21.1 is installed and exposed to network access.

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 vendor-provided patch for DAQFactory 20.7 once released; until then, restrict network access to DAQFactory systems and isolate from untrusted networks given the critical severity and RCE capability.

Recommended fix Moderate confidence

DAQFactory 21.1

  1. 1. Back up all existing DAQFactory project files and configurations
  2. 2. Download DAQFactory version 21.1 or later from the official AzeoTech website
  3. 3. Install the new version following the standard installation procedure
  4. 4. Restore project files from the backup
  5. 5. Verify that all critical functionality operates correctly after the upgrade
  6. 6. Test that the previously vulnerable functionality is now properly functioning

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

Fix this in Daqfactory Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-66588 — 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-66588 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