azeotech CVE Vulnerabilities & Metrics

Focus on azeotech vulnerabilities and metrics.

Last updated: 16 Jan 2026, 23:25 UTC

About azeotech Security Exposure

This page consolidates all known Common Vulnerabilities and Exposures (CVEs) associated with azeotech. We track both calendar-based metrics (using fixed periods) and rolling metrics (using gliding windows) to give you a comprehensive view of security trends and risk evolution. Use these insights to assess risk and plan your patching strategy.

For a broader perspective on cybersecurity threats, explore the comprehensive list of CVEs by vendor and product. Stay updated on critical vulnerabilities affecting major software and hardware providers.

Global CVE Overview

Total azeotech CVEs: 11
Earliest CVE date: 30 Dec 2009, 21:30 UTC
Latest CVE date: 11 Dec 2025, 21:15 UTC

Latest CVE reference: CVE-2025-66590

Rolling Stats

30-day Count (Rolling): 0
365-day Count (Rolling): 5

Calendar-based Variation

Calendar-based Variation compares a fixed calendar period (e.g., this month versus the same month last year), while Rolling Growth Rate uses a continuous window (e.g., last 30 days versus the previous 30 days) to capture trends independent of calendar boundaries.

Variations & Growth

Month Variation (Calendar): -100.0%
Year Variation (Calendar): 0%

Month Growth Rate (30-day Rolling): -100.0%
Year Growth Rate (365-day Rolling): 0.0%

Monthly CVE Trends (current vs previous Year)

Annual CVE Trends (Last 20 Years)

Critical azeotech CVEs (CVSS ≥ 9) Over 20 Years

CVSS Stats

Average CVSS: 4.04

Max CVSS: 10.0

Critical CVEs (≥9): 2

CVSS Range vs. Count

Range Count
0.0-3.9 7
4.0-6.9 3
7.0-8.9 2
9.0-10.0 2

CVSS Distribution Chart

Top 5 Highest CVSS azeotech CVEs

These are the five CVEs with the highest CVSS scores for azeotech, sorted by severity first and recency.

All CVEs for azeotech

CVE-2025-66590 azeotech vulnerability CVSS: 0 11 Dec 2025, 21:15 UTC

In AzeoTech DAQFactory release 20.7 (Build 2555), an Out-of-bounds Write vulnerability can be exploited by an attacker to cause the program to write data past the end of an allocated memory buffer. This can lead to arbitrary code execution or a system crash.

CVE-2025-66589 azeotech vulnerability CVSS: 0 11 Dec 2025, 21:15 UTC

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.

CVE-2025-66588 azeotech vulnerability CVSS: 0 11 Dec 2025, 21:15 UTC

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.

CVE-2025-66586 azeotech vulnerability CVSS: 0 11 Dec 2025, 21:15 UTC

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.

CVE-2025-66585 azeotech vulnerability CVSS: 0 11 Dec 2025, 21:15 UTC

In AzeoTech DAQFactory release 20.7 (Build 2555), a Use After Free 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.

CVE-2021-42701 azeotech vulnerability CVSS: 2.6 05 Nov 2021, 16:15 UTC

An attacker could prepare a specially crafted project file that, if opened, would attempt to connect to the cloud and trigger a man in the middle (MiTM) attack. This could allow an attacker to obtain credentials and take over the user’s cloud account.

CVE-2021-42699 azeotech vulnerability CVSS: 4.3 05 Nov 2021, 16:15 UTC

The affected product is vulnerable to cookie information being transmitted as cleartext over HTTP. An attacker can capture network traffic, obtain the user’s cookie and take over the account.

CVE-2021-42698 azeotech vulnerability CVSS: 6.8 05 Nov 2021, 16:15 UTC

Project files are stored memory objects in the form of binary serialized data that can later be read and deserialized again to instantiate the original objects in memory. Malicious manipulation of these files may allow an attacker to corrupt memory.

CVE-2021-42543 azeotech vulnerability CVSS: 7.5 05 Nov 2021, 16:15 UTC

The affected application uses specific functions that could be abused through a crafted project file, which could lead to code execution, system reboot, and system shutdown.

CVE-2017-5147 azeotech vulnerability CVSS: 4.6 09 Sep 2017, 01:29 UTC

An Uncontrolled Search Path Element issue was discovered in AzeoTech DAQFactory versions prior to 17.1. An uncontrolled search path element vulnerability has been identified, which may execute malicious DLL files that have been placed within the search path.

CVE-2017-12699 azeotech vulnerability CVSS: 3.6 09 Sep 2017, 01:29 UTC

An Incorrect Default Permissions issue was discovered in AzeoTech DAQFactory versions prior to 17.1. Local, non-administrative users may be able to replace or modify original application files with malicious ones.

CVE-2011-3492 azeotech vulnerability CVSS: 10.0 16 Sep 2011, 14:28 UTC

Stack-based buffer overflow in Azeotech DAQFactory 5.85 build 1853 and earlier allows remote attackers to cause a denial of service (crash) and execute arbitrary code via a crafted NETB packet to UDP port 20034.

CVE-2011-2956 azeotech vulnerability CVSS: 7.8 28 Jul 2011, 18:55 UTC

AzeoTech DAQFactory before 5.85 (Build 1842) does not perform authentication for certain signals, which allows remote attackers to cause a denial of service (system reboot or shutdown) via a signal.

CVE-2009-4480 azeotech vulnerability CVSS: 9.3 30 Dec 2009, 21:30 UTC

Buffer overflow in the web service in AzeoTech DAQFactory 5.77 might allow remote attackers to execute arbitrary code via unspecified vectors, as demonstrated by a certain module in VulnDisco Pack Professional 7.16 through 8.11. NOTE: as of 20091229, this disclosure has no actionable information. However, because the VulnDisco Pack author is a reliable researcher, the issue is being assigned a CVE identifier for tracking purposes.