Frederic Cambus

The issue is related to a heap-based buffer overflow in the srcnext() function, located in the z02.c file.

The issue is related to a buffer overflow in the StringQuotedWord() function, located in the z39.c file.

The issue is related to an out-of-bounds write in the `read colordef` function in `read.c`.

The issue is a stack-based buffer overflow in the `get signed expression()` function, located in setparse.c, which can be triggered by a crafted .m65 file.

The issue is a stack-based buffer overflow in the `to comma()` function, located in `asm.c`, which can be triggered by a crafted `.m65` file.

The issue is a stack-based buffer overflow in the `parse expr()` function, located in setparse.c, which can be triggered by a crafted .m65 file.

The issue is related to a stack-based buffer overflow in the `read textobject` function in `read.c` due to an incorrect use of `sscanf`. This can lead to a denial of service. The vulnerability may allow a remote attacker to cause a service disruption.

The issue is related to a heap-based buffer overflow in the define array function within the variables.c file. This overflow can be triggered by crafted BASIC source code.

The issue is a stack-based buffer overflow in the `fileio openin` function located in `fileio.c`. This occurs when the software processes crafted BASIC source code.

The issue is a stack-based buffer overflow in the fileio openout function in fileio.c, which can be triggered by crafted BASIC source code.

The issue is related to a buffer overflow in the `calc arrow` function, which can be exploited by an attacker using a specially crafted .fig file, potentially leading to a denial of service.

The issue is a heap-based buffer overflow in the `do msg()` function located in support.c. This overflow can potentially lead to arbitrary code execution, allowing an attacker to execute malicious code on the affected system.