MAWK 1.3.3-17 and prior contains a stack-based buffer overflow vulnerability that allows attackers to execute arbitrary code by exploiting inadequate boundary checks on user-supplied input. Attackers can craft malicious input that overflows the stack buffer and execute a return-oriented programming chain to spawn a shell with application privileges.

Last updated 2 April 2026

NCurse is vulnerable to a denial of service, caused by a segmentation fault in the ncwrapentry(). By persuading a victim to open a specially crafted content, a remote attacker could exploit this vulnerability to cause a denial of service condition.

Accessibility. A privacy issue was addressed with improved private data redaction for log entries.

Accessibility. A privacy issue was addressed with improved private data redaction for log entries.

Accessibility. A privacy issue was addressed with improved private data redaction for log entries.

Accessibility. A privacy issue was addressed with improved private data redaction for log entries.

Accessibility. A privacy issue was addressed with improved private data redaction for log entries.

Accessibility. A privacy issue was addressed with improved private data redaction for log entries.

xterm before 380 supports ReGIS reporting for character-set names even if they have unexpected characters (i.e., neither alphanumeric nor underscore), aka a pointer/overflow issue. This can only occur for xterm installations that are configured at compile time to use a certain experimental feature.

Accounts. A privacy issue was addressed with improved private data redaction for log entries.

xterm before 375 allows code execution via font ops, e.g., because an OSC 50 response may have Ctrl-g and therefore lead to command execution within the vi line-editing mode of Zsh. NOTE: font ops are not allowed in the xterm default configurations of some Linux distributions.

Accelerate Framework. A memory consumption issue was addressed with improved memory handling.

xterm through Patch 370, when Sixel support is enabled, allows attackers to trigger a buffer overflow in setsixel in graphicssixel.c via crafted text.

Accelerate Framework. A memory consumption issue was addressed with improved memory handling.

A crash was reported in xterm prior to patch #366 when processing a specially crafted sequence of combining characters. The cause is an out of bounds write, which may be exploitable to cause arbitrary code execution.

https://www.openwall.com/lists/oss-security/2021/02/09/7 https://invisible-island.net/xterm/xterm.log.html

GNU ncurses could allow a remote attacker to obtain sensitive information, caused by a heap-based buffer over-read in the ncfindentry function in tinfo/comphash.c in the terminfo library. By persuading a victim to open a specially-crafted file, an attacker could exploit this vulnerability to obtain sensitive information.

GNU ncurses could allow a remote attacker to obtain sensitive information, caused by a heap-based buffer over-read in the fmtentry function in tinfo/comphash.c in the terminfo library. By persuading a victim to open a specially-crafted file, an attacker could exploit this vulnerability to obtain sensitive information.

DISPUTED In ncurses, possibly a 6.x version, there is a NULL pointer dereference at the function ncnamematch that will lead to a denial of service attack. NOTE: the original report stated version 6.1, but the issue did not reproduce for that version according to the maintainer or a reliable third-party.

In ncurses 6.1, there is a NULL pointer dereference at function ncparseentry in parseentry.c that will lead to a denial of service attack. The product proceeds to the dereference code path even after a "dubious character ' in name or alias field" detection.

Stack-based buffer overflow in the ncwriteentry function in tinfo/writeentry.c in ncurses 6.0 allows attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a crafted terminfo file, as demonstrated by tic.

There is an illegal address access in the ncsavestr function in allocentry.c in ncurses 6.0. It will lead to a remote denial of service attack.

There is an illegal address access in the function ncreadentrysource() in progs/tic.c in ncurses 6.0 that might lead to a remote denial of service attack.

There is an infinite loop in the nextchar function in compscan.c in ncurses 6.0, related to libtic. A crafted input will lead to a remote denial of service attack.

There is an illegal address access in the function dumpuses() in progs/dumpentry.c in ncurses 6.0 that might lead to a remote denial of service attack.

There is an illegal address access in the ncsafestrcat function in strings.c in ncurses 6.0 that will lead to a remote denial of service attack.

There is an illegal address access in the function postprocesstermcap() in parseentry.c in ncurses 6.0 that will lead to a remote denial of service attack.

There is an illegal address access in the fmtentry function in progs/dumpentry.c in ncurses 6.0 that might lead to a remote denial of service attack.

In ncurses 6.0, there is a NULL Pointer Dereference in the ncparseentry function of tinfo/parseentry.c. It could lead to a remote denial of service attack if the terminfo library code is used to process untrusted terminfo data.

In ncurses 6.0, there is an attempted 0xffffffffffffffff access in the appendacs function of tinfo/parseentry.c. It could lead to a remote denial of service attack if the terminfo library code is used to process untrusted terminfo data.