Han0Nly

The issue is a null pointer dereference in the libr/bin/format/mach0/mach0.c file of radare2. It is likely to be exploitable. The problem is related to a heap buffer overflow, for which a more general description can be found in the CWE definition.

The issue is related to improper validation of array index, which can lead to a heap overflow and may be exploitable. This is a type of heap buffer overflow.

The issue is related to an out-of-bounds write in the libr/bin/format/ne/ne.c file, which can cause a heap buffer overflow. This may be exploitable. The heap buffer overflow occurs when more data is written to a buffer than it is designed to hold, causing extra data to spill over into adjacent areas of memory.

A heap buffer overflow issue exists in the libr/bin/format/mach0/mach0.c file of the radare2 GitHub repository. This issue is likely exploitable, especially when the address sanitizer is disabled during compilation, allowing the program to execute into the `r str ncpy` function.

A carefully crafted RAR archive can trigger an infinite loop while extracting the archive. The impact depends on how the application uses the library and whether files can be provided by malignant users.

A stack-based buffer overflow was discovered in the component `ByteBuffer.append`, which allows attackers to cause a Denial of Service (DoS) via a crafted PDF file.