Multiple vulnerabilities have been found in w3m, the worst of which could lead to the execution of arbitrary code.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| www-client/w3m | * | < 0.5.3-r9 | >= 0.5.3-r9 |
w3m is a text based WWW browser.
Multiple vulnerabilities have been discovered in w3m. Please review the CVE identifiers referenced below for details.
A remote attacker could execute arbitrary code with the privileges of the process or cause a Denial of Service condition via a maliciously crafted HTML file.
There is no known workaround at this time.
All w3m users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=www-client/w3m-0.5.3-r9"
An error in the hostname matching of w3m might enable remote attackers to conduct man-in-the-middle attacks.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| www-client/w3m | * | < 0.5.2-r4 | >= 0.5.2-r4 |
w3m is a text based WWW browser.
A SSL spoofing vulnerability has been discovered in w3m. Please review the CVE identifier referenced below for details.
A remote attacker might employ a specially crafted certificate to conduct man-in-the-middle attacks on SSL connections made using w3m.
There is no known workaround at this time.
All w3m users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=www-client/w3m-0.5.2-r4"
w3m does not correctly handle format string specifiers in SSL certificates.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| www-client/w3m | * | < 0.5.1-r4 | >= 0.5.1-r4 |
w3m is a multi-platform text-based web browser.
w3m in -dump or -backend mode does not correctly handle printf() format string specifiers in the Common Name (CN) field of an X.509 SSL certificate.
An attacker could entice a user to visit a malicious website that would load a specially crafted X.509 SSL certificate containing "%n" or other format string specifiers, possibly resulting in the execution of arbitrary code with the rights of the user running w3m.
There is no known workaround at this time.
All w3m users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=www-client/w3m-0.5.1-r4"