See how libmodbus compares to other vendors in security performance
libmodbus v3.1.10 has a heap-based buffer overflow vulnerability in readiostatus function in src/modbus.c.
Stack-based Buffer Overflow vulnerability in libmodbus v3.1.10 allows to overflow the buffer allocated for the Modbus response if the function tries to reply to a Modbus request with an unexpected length.
An issue was discovered in libmodbus before 3.0.7 and 3.1.x before 3.1.5. There is an out-of-bounds read for the MODBUSFCWRITEMULTIPLEREGISTERS case, aka VD-1301.
An issue was discovered in libmodbus before 3.0.7 and 3.1.x before 3.1.5. There is an out-of-bounds read for the MODBUSFCWRITEMULTIPLECOILS case, aka VD-1302.
A flaw was found in libmodbus. A heap-based buffer overflow in modbusreceivemsg.
References:
https://github.com/stephane/libmodbus/issues/614
libmodbus v3.1.10 is vulnerable to Buffer Overflow via the modbuswritebits function. This issue can be triggered when the function is fed with specially crafted input, which leads to out-of-bounds read and can potentially cause a crash or other unintended behaviors.
libmodbus v3.1.6 was discovered to contain a use-after-free via the ctx->backend pointer. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted message sent to the unit-test-server.
libmodbus v3.1.6 was discovered to contain a heap overflow via the modbusmappingfree() function.
A Denial of Service (DoS) vulnerability exists in the receive loop of libmodbus 3.1.12 when running on Windows. The issue stems from improper timeout management during network read operations.
An invalid pointer in the modbusreceive() function of libmodbus v3.1.6 allows attackers to cause a Denial of Service (DoS) via a crafted message sent to the unit-test-server.
A flaw was found in libmodbus. A heap-based buffer overflow in modbusreceivemsg.
References:
https://github.com/stephane/libmodbus/issues/614