What is the severity of CVE-2016-9624?

CVE-2016-9624 has a severity rating that indicates it can cause a denial of service due to segmentation faults.

How do I fix CVE-2016-9624?

To fix CVE-2016-9624, upgrade w3m to version 0.5.3-33 or later.

What types of attacks does CVE-2016-9624 allow?

CVE-2016-9624 allows remote attackers to execute a denial of service attack by causing the application to crash.

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

CVE-2016-9624 affects versions of w3m prior to 0.5.3-33.

Who is affected by CVE-2016-9624?

Users of the w3m fork from Tatsuya Kinoshita before version 0.5.3-33 are affected by CVE-2016-9624.

Vulnerability/
CVE-2016-9624

medium

6.5

CWE

476

12/12/2016

6/8/2024

CVE-2016-9624: Null Pointer Dereference

First published: Mon Dec 12 2016(Updated: )

An issue was discovered in the Tatsuya Kinoshita w3m fork before 0.5.3-33. w3m allows remote attackers to cause a denial of service (segmentation fault and crash) via a crafted HTML page.

Credit: cve@mitre.org

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

Remedy

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

Remedy

https://github.com/tats/w3m/issues/35

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-9624?
CVE-2016-9624 has a severity rating that indicates it can cause a denial of service due to segmentation faults.
How do I fix CVE-2016-9624?
To fix CVE-2016-9624, upgrade w3m to version 0.5.3-33 or later.
What types of attacks does CVE-2016-9624 allow?
CVE-2016-9624 allows remote attackers to execute a denial of service attack by causing the application to crash.
Which versions of w3m are affected by CVE-2016-9624?
CVE-2016-9624 affects versions of w3m prior to 0.5.3-33.
Who is affected by CVE-2016-9624?
Users of the w3m fork from Tatsuya Kinoshita before version 0.5.3-33 are affected by CVE-2016-9624.

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

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-9624?
CVE-2016-9624 has a severity rating that indicates it can cause a denial of service due to segmentation faults.
How do I fix CVE-2016-9624?
To fix CVE-2016-9624, upgrade w3m to version 0.5.3-33 or later.
What types of attacks does CVE-2016-9624 allow?
CVE-2016-9624 allows remote attackers to execute a denial of service attack by causing the application to crash.
Which versions of w3m are affected by CVE-2016-9624?
CVE-2016-9624 affects versions of w3m prior to 0.5.3-33.
Who is affected by CVE-2016-9624?
Users of the w3m fork from Tatsuya Kinoshita before version 0.5.3-33 are affected by CVE-2016-9624.