CVE-2010-2074Not scoredCWE-20

CVE-2010-2074: W3m vulnerability

W3m

Vendor fix available · Affected: W3m · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

1.5%probability of exploitation in the next 30 days

74th percentile

050100

Higher than 74% of scored CVEs

Not scored yet. The CVE record carries no CVSS score.

DescriptionCVE.org

istream.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 domain name in the (1) subject's Common Name or (2) Subject Alternative Name field of an X.509 certificate, which allows man-in-the-middle attackers to spoof arbitrary SSL servers via a crafted certificate issued by a legitimate Certification Authority, a related issue to CVE-2009-2408.

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Improper Input Validation · Input Validation and Logic
Vendor: W3m
Published: June 2010
Band: Possible (1 to 10%), June 2010

CoverageNo articles yet

No CyberSIXT article names CVE-2010-2074 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.