dbcve.org
DaqfactoryApplication · Azeotech

CVE-2025-66589

CRITICAL · 9.1 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 Out-of-bounds Read vulnerability can be exploited by an attacker to cause the program to read data past the end of an allocated buffer. This could allow an attacker to disclose information or cause a system crash.

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

An out-of-bounds read vulnerability exists in AzeoTech DAQFactory release 20.7 (Build 2555). The vulnerability allows an attacker to read data beyond the boundaries of an allocated memory buffer, potentially exposing sensitive information or causing the application to crash.

MitigationApply vendor-supplied patch when available; until then, restrict network access to DAQFactory and sanitize all external inputs to prevent exploitation.

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
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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
    Open DAQFactory and navigate to Help > About, or check the Windows Programs and Features list for the installed version number and build
    Affected if The installed version is 20.7 or any version below 21.1
  2. Confirm the exact build number
    In DAQFactory, go to Help > About and note the full build number (for example, Build 2555 was the vulnerable release)
    Affected if Build number is 2555 or falls within releases prior to 21.1
  3. Verify network exposure of DAQFactory service
    Check if DAQFactory is bound to network interfaces or listening on TCP/UDP ports by reviewing the application configuration and running 'netstat -an' to look for listening ports associated with DAQFactory
    Affected if DAQFactory is listening on exposed network ports without firewall restrictions
  4. Assess external input handling
    Review any sequence scripts, Express sequences, or communication drivers that process external data from network sources or file inputs
    Affected if External or network-sourced inputs are processed without input validation routines in place

The environment is affected if DAQFactory version is below 21.1 and the application processes external inputs or is network-accessible, as the out-of-bounds read can be triggered by crafted data.

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-supplied patch when available; until then, restrict network access to DAQFactory and sanitize all external inputs to prevent exploitation.

Recommended fix Moderate confidence

DAQFactory version 21.1

  1. 1. Identify the current installed version of AzeoTech DAQFactory by accessing the program's About or Help section
  2. 2. Verify the current version is below 21.1 (vulnerable if < 21.1)
  3. 3. Back up all existing DAQFactory project files, sequences, and configuration data to a secure location
  4. 4. Navigate to the official AzeoTech website or trusted download source to obtain DAQFactory version 21.1
  5. 5. Download the version 21.1 installer for your platform
  6. 6. Run the installer and follow the prompts to upgrade DAQFactory to version 21.1
  7. 7. After installation, verify the new version by checking About DAQFactory confirms version 21.1 is installed
  8. 8. Restore backed-up project files and validate critical applications function correctly

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

Fix this in Daqfactory Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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