What is the severity of CVE-2016-9442?

CVE-2016-9442 is classified as a high severity vulnerability due to its potential for memory corruption attacks.

How do I fix CVE-2016-9442?

To fix CVE-2016-9442, upgrade to w3m version 0.5.3-31 or later.

What type of attacks does CVE-2016-9442 allow?

CVE-2016-9442 allows remote attackers to exploit memory corruption via crafted HTML pages.

Which versions of w3m are affected by CVE-2016-9442?

CVE-2016-9442 affects w3m versions 0.5.3-30 and earlier.

Who is the vendor associated with CVE-2016-9442?

CVE-2016-9442 is associated with the Tatsuya Kinoshita w3m fork and the original w3m project.

Vulnerability/
CVE-2016-9442

medium

6.5

CWE

119

12/12/2016

6/8/2024

CVE-2016-9442: Buffer Overflow

First published: Mon Dec 12 2016(Updated: )

An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-31. w3m allows remote attackers to cause memory corruption in certain conditions via a crafted HTML page.

Credit: cve@mitre.org cve@mitre.org

Affected Software	Affected Version	How to fix
w3m	<=0.5.3-30
w3m	<=0.5.3-30

Remedy

https://github.com/tats/w3m/blob/master/ChangeLog

Remedy

https://github.com/tats/w3m/commit/d43527cfa0dbb3ccefec4a6f7b32c1434739aa29

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-9442?
CVE-2016-9442 is classified as a high severity vulnerability due to its potential for memory corruption attacks.
How do I fix CVE-2016-9442?
To fix CVE-2016-9442, upgrade to w3m version 0.5.3-31 or later.
What type of attacks does CVE-2016-9442 allow?
CVE-2016-9442 allows remote attackers to exploit memory corruption via crafted HTML pages.
Which versions of w3m are affected by CVE-2016-9442?
CVE-2016-9442 affects w3m versions 0.5.3-30 and earlier.
Who is the vendor associated with CVE-2016-9442?
CVE-2016-9442 is associated with the Tatsuya Kinoshita w3m fork and the original w3m project.

agent/type
agent/remedy
agent/author
agent/softwarecombine
agent/references
agent/severity
agent/weakness
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/description
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-api
source/NVD
agent/software-canonical-lookup
agent/software-canonical-lookup-request
collector/nvd-index
vendor/tats
canonical/w3m
version/w3m/0.5.3-30
vendor/w3m project

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2016-9442?
CVE-2016-9442 is classified as a high severity vulnerability due to its potential for memory corruption attacks.
How do I fix CVE-2016-9442?
To fix CVE-2016-9442, upgrade to w3m version 0.5.3-31 or later.
What type of attacks does CVE-2016-9442 allow?
CVE-2016-9442 allows remote attackers to exploit memory corruption via crafted HTML pages.
Which versions of w3m are affected by CVE-2016-9442?
CVE-2016-9442 affects w3m versions 0.5.3-30 and earlier.
Who is the vendor associated with CVE-2016-9442?
CVE-2016-9442 is associated with the Tatsuya Kinoshita w3m fork and the original w3m project.