w3m vulnerabilities

An issue was discovered in w3m before version 0.5.3-31 related to a buffer overflow in the formUpdateBuffer function. Remote attackers can cause a denial of service (crash) and possibly execute arbitrary code via a crafted HTML page.

An issue was discovered in w3m before version 0.5.3-31 related to a heap-based buffer overflow in the addMultirowsForm function. This allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted HTML page.

An issue was discovered in the Tatsuya Kinoshita w3m fork before version 0.5.3-31. Integer overflow vulnerability in the renderTable function in w3m allows remote attackers to cause a denial of service (OOM) and possibly execute arbitrary code via a crafted HTML page.

An issue was discovered in the w3m fork before version 0.5.3-31, involving a heap-based buffer overflow in the addMultirowsForm function. This allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted HTML page.

An issue was discovered in w3m before version 0.5.3-31 related to improper validation of tag attribute values, which can lead to heap buffer overflow and program crashes. Remote attackers may exploit this vulnerability to potentially execute arbitrary code via a crafted HTML page.

An issue was discovered in the w3m fork before version 0.5.3-31. Heap-based buffer overflow in w3m allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted HTML page.

An issue was discovered in w3m before version 0.5.3-31 related to the feed_table_tag function, which does not properly validate the table span value. This allows remote attackers to cause a denial of service (stack and/or heap buffer overflow) and possibly execute arbitrary code via a crafted HTML page.

An out-of-bounds read flaw was found in w3m, in the growbuf_to_Str function in indep.c. This issue may allow an attacker to cause a denial of service through a crafted HTML file.

An out-of-bounds read flaw was found in w3m, in the Strnew_size function in Str.c. This issue may allow an attacker to cause a denial of service through a crafted HTML file.