AzeoTech vulnerabilities
We track 7 vulnerabilities in AzeoTech products. 7 are rated high or critical, and none are known to be exploited. The most recent was published on June 25, 2026.
Latest AzeoTech vulnerabilities
- 7.8 High severity
DAQFactory: Use After Free
In AzeoTech DAQFactory versions 21.1 and prior, a Use After Free vulnerability can be exploited by an attacker using specially crafted .ctl files which can result in code execution.
- 7.8 High severity
DAQFactory: Access of Resource Using Incompatible Type
In AzeoTech DAQFactory versions 21.1 and prior, a Type Confusion vulnerability can be exploited by an attacker using specially crafted .ctl files which can result in code execution.
- 9.8 Critical severity
DAQFactory: Out-of-bounds Write
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.
- 9.1 Critical severity
DAQFactory: Out-of-bounds Read
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
- 9.8 Critical severity
DAQFactory: Access of Uninitialized Pointer
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.
- 7.8 High severity
DAQFactory: Access of Resource Using Incompatible Type
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
- 7.8 High severity
DAQFactory: Use After Free
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.