pkg:Debian/w3m

All known vulnerabilities

• HIGH8.8CVE-2016-9429An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31.
  from 0, < 0.5.3-30
• HIGH8.8CVE-2016-9428An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31.
  from 0, < 0.5.3-30
• HIGH8.8CVE-2016-9426An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31.
  from 0, < 0.5.3-30
• HIGH8.8CVE-2016-9425An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31.
  from 0, < 0.5.3-30
• HIGH8.8CVE-2016-9424An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31.
  from 0, < 0.5.3-30
• HIGH8.8CVE-2016-9423An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31.
  from 0, < 0.5.3-30
• HIGH8.8CVE-2016-9422An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31.
  from 0, < 0.5.3-30
• HIGH7.8CVE-2022-38223w3m - security update
  from 0, < 0.5.3-37+deb10u1
• HIGH7.8CVE-2022-38223w3m - security update
  from 0, < 0.5.3+git20210102-6+deb11u1
• HIGH7.5CVE-2018-6197w3m through 0.5.3 is prone to a NULL pointer dereference flaw in formUpdateBuffer in form.c.
  from 0, < 0.5.3-36
• HIGH7.5CVE-2018-6196w3m - security update
  from 0, < 0.5.3-36
• HIGH7.5CVE-2018-6196w3m - security update
  from 0, < 0.5.3-19+deb8u3
• MEDIUM6.5CVE-2016-9436parsetagx.c in w3m before 0.5.3+git20161009 does not properly initialize values, which allows remote attackers to crash the application via…
  from 0, < 0.5.3-30
• MEDIUM6.5CVE-2016-9435The HTMLtagproc1 function in file.c in w3m before 0.5.3+git20161009 does not properly initialize values, which allows remote attackers to c…
  from 0, < 0.5.3-30
• MEDIUM6.5CVE-2016-9633An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33.
  from 0, < 0.5.3-33
• MEDIUM6.5CVE-2016-9632An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33.
  from 0, < 0.5.3-33
• MEDIUM6.5CVE-2016-9631An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33.
  from 0, < 0.5.3-33
• MEDIUM6.5CVE-2016-9630An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33.
  from 0, < 0.5.3-33
• MEDIUM6.5CVE-2016-9629An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33.
  from 0, < 0.5.3-33
• MEDIUM6.5CVE-2016-9628An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33.
  from 0, < 0.5.3-33
• MEDIUM6.5CVE-2016-9627An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33.
  from 0, < 0.5.3-33
• MEDIUM6.5CVE-2016-9626An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33.
  from 0, < 0.5.3-33
• MEDIUM6.5CVE-2016-9625An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33.
  from 0, < 0.5.3-33
• MEDIUM6.5CVE-2016-9624An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33.
  from 0, < 0.5.3-33
• MEDIUM6.5CVE-2016-9623An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33.
  from 0, < 0.5.3-33
• MEDIUM6.5CVE-2016-9622An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33.
  from 0, < 0.5.3-33
• MEDIUM6.5CVE-2016-9443An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31.
  from 0, < 0.5.3-30
• MEDIUM6.5CVE-2016-9442An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31.
  from 0, < 0.5.3-30
• MEDIUM6.5CVE-2016-9441An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31.
  from 0, < 0.5.3-30
• MEDIUM6.5CVE-2016-9440An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31.
  from 0, < 0.5.3-30
• MEDIUM6.5CVE-2016-9439An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31.
  from 0, < 0.5.3-33
• MEDIUM6.5CVE-2016-9438An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31.
  from 0, < 0.5.3-30
• MEDIUM6.5CVE-2016-9437An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31.
  from 0, < 0.5.3-30
• MEDIUM6.5CVE-2016-9434An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31.
  from 0, < 0.5.3-30
• MEDIUM6.5CVE-2016-9433An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31.
  from 0, < 0.5.3-30
• MEDIUM6.5CVE-2016-9432An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31.
  from 0, < 0.5.3-30
• MEDIUM6.5CVE-2016-9431An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31.
  from 0, < 0.5.3-30
• MEDIUM6.5CVE-2016-9430An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31.
  from 0, < 0.5.3-30
• MEDIUM5.5CVE-2023-4255An out-of-bounds write issue has been discovered in the backspace handling of the checkType() function in etc.c within the W3M application.
  from 0
• MEDIUM5.5CVE-2023-38253An out-of-bounds read flaw was found in w3m, in the growbuf_to_Str function in indep.c.
  from 0
• MEDIUM5.5CVE-2023-38252An out-of-bounds read flaw was found in w3m, in the Strnew_size function in Str.c.
  from 0
• MEDIUM4.7CVE-2018-6198w3m through 0.5.3 does not properly handle temporary files when the ~/.w3m directory is unwritable, which allows a local attacker to craft…
  from 0, < 0.5.3-36
• —CVE-2010-2074istream.c in w3m 0.5.2 and possibly other versions, when ssl_verify_server is enabled, does not properly handle a '\0' character in a domai…
  from 0, < 0.5.2-5
• —CVE-2006-6772Format string vulnerability in the inputAnswer function in file.c in w3m before 0.5.2, when run with the dump or backend option, allows rem…
  from 0, < 0.5.1-5.1
• —CVE-2002-1348w3m before 0.3.2.2 does not properly escape HTML tags in the ALT attribute of an IMG tag, which could allow remote attackers to access file…
  from 0, < 0.3.2.2-1
• —CVE-2002-1335w3m - missing HTML quoting
  from 0, < 0.3.2.2-1
• —CVE-2002-1335w3m - missing HTML quoting
  from 0, < 0.3-2.4