TA
Vendor
Tats
40
CVEs
0
On KEV
0
New 30D
Products
Recent CVEs
| CVE | Product | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2023-4255 | W3 W3m Tats | 5.5 | Dec 21 | An out-of-bounds write issue has been discovered in the backspace handling of the checkType() function in etc.c within the W3M application |
| CVE-2023-38253 | W3 W3m Tats | 5.5 | Jul 14 | An out-of-bounds read flaw was found in w3m, in the growbuf_to_Str function in indep.c |
| CVE-2023-38252 | W3 W3m Tats | 5.5 | Jul 14 | An out-of-bounds read flaw was found in w3m, in the Strnew_size function in Str.c |
| CVE-2022-38223 | W3 W3m Tats | 7.8 | Aug 15 | There is an out-of-bounds write in checkType located in etc.c in w3m 0.5.3 |
| CVE-2018-6198 | W3 W3m Tats | 4.7 | Jan 25 | w3m through 0.5.3 does not properly handle temporary files when the ~/.w3m directory is unwritable, which allows a local attacker to craft a symlink attack to overwrite arbitrary… |
| CVE-2018-6197 | W3 W3m Tats | 7.5 | Jan 25 | w3m through 0.5.3 is prone to a NULL pointer dereference flaw in formUpdateBuffer in form.c |
| CVE-2018-6196 | W3 W3m Tats | 7.5 | Jan 25 | w3m through 0.5.3 is prone to an infinite recursion flaw in HTMLlineproc0 because the feed_table_block_tag function in table.c does not prevent a negative indent value |
| CVE-2016-9436 | W3 W3m Tats | 6.5 | Jan 20 | parsetagx.c in w3m before 0.5.3+git20161009 does not properly initialize values, which allows remote attackers to crash the application via a crafted html file, related to a <i>… |
| CVE-2016-9435 | W3 W3m Tats | 6.5 | Jan 20 | The HTMLtagproc1 function in file.c in w3m before 0.5.3+git20161009 does not properly initialize values, which allows remote attackers to crash the application via a crafted html… |
| CVE-2016-9633 | W3 W3m Tats | 6.5 | Dec 12 | An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33 |
| CVE-2016-9632 | W3 W3m Tats | 6.5 | Dec 12 | An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33 |
| CVE-2016-9631 | W3 W3m Tats | 6.5 | Dec 12 | An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33 |
| CVE-2016-9630 | W3 W3m Tats | 6.5 | Dec 12 | An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33 |
| CVE-2016-9629 | W3 W3m Tats | 6.5 | Dec 12 | An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33 |
| CVE-2016-9628 | W3 W3m Tats | 6.5 | Dec 12 | An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33 |
| CVE-2016-9627 | W3 W3m Tats | 6.5 | Dec 12 | An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33 |
| CVE-2016-9626 | W3 W3m Tats | 6.5 | Dec 12 | An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33 |
| CVE-2016-9625 | W3 W3m Tats | 6.5 | Dec 12 | An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33 |
| CVE-2016-9624 | W3 W3m Tats | 6.5 | Dec 12 | An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33 |
| CVE-2016-9623 | W3 W3m Tats | 6.5 | Dec 12 | An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33 |
| CVE-2016-9622 | W3 W3m Tats | 6.5 | Dec 12 | An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33 |
| CVE-2016-9443 | W3 W3m Tats | 6.5 | Dec 12 | An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31 |
| CVE-2016-9442 | W3 W3m Tats | 6.5 | Dec 12 | An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31 |
| CVE-2016-9441 | W3 W3m Tats | 6.5 | Dec 12 | An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31 |
| CVE-2016-9440 | W3 W3m Tats | 6.5 | Dec 12 | An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31 |
| CVE-2016-9439 | W3 W3m Tats | 6.5 | Dec 12 | An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31 |
| CVE-2016-9438 | W3 W3m Tats | 6.5 | Dec 12 | An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31 |
| CVE-2016-9437 | W3 W3m Tats | 6.5 | Dec 12 | An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31 |
| CVE-2016-9434 | W3 W3m Tats | 6.5 | Dec 12 | An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31 |
| CVE-2016-9433 | W3 W3m Tats | 6.5 | Dec 12 | An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31 |
| CVE-2016-9432 | W3 W3m Tats | 6.5 | Dec 12 | An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31 |
| CVE-2016-9431 | W3 W3m Tats | 6.5 | Dec 12 | An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31 |
| CVE-2016-9430 | W3 W3m Tats | 6.5 | Dec 12 | An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31 |
| CVE-2016-9429 | W3 W3m Tats | 8.8 | Dec 12 | An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31 |
| CVE-2016-9428 | W3 W3m Tats | 8.8 | Dec 12 | An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31 |
| CVE-2016-9426 | W3 W3m Tats | 8.8 | Dec 12 | An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31 |
| CVE-2016-9425 | W3 W3m Tats | 8.8 | Dec 12 | An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31 |
| CVE-2016-9424 | W3 W3m Tats | 8.8 | Dec 12 | An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31 |
| CVE-2016-9423 | W3 W3m Tats | 8.8 | Dec 12 | An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31 |
| CVE-2016-9422 | W3 W3m Tats | 8.8 | Dec 12 | An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31 |