Skip to content
Fencer Intel
medium 6.8

CVE-2010-2074 json

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 domai…

published 16y ago modified 4mo ago also EUVD-2010-2093

cvss
6.8
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.5%
EPSS 1.5% chance of exploitation in 30 days, percentile 74%
public exploits
0
none known

Summary

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.

Patch / fix

  • w3m Debian 14, Debian 13, Debian 12 0.5.2-5

debian advisories DEBIAN-CVE-2010-2074

  • w3m RHEL 5 0.5.1-17.el5_5
  • w3m-img RHEL 5 0.5.1-17.el5_5

red hat advisories RHSA-2010:0565

  • w3m SLES for SAP 11 SP4, SLES 11 SP4 0.5.3.git20161120-4.1

suse advisories SUSE-SU-2016:3046-1

  • w3m openSUSE Tumbleweed 0.5.3.git20161120-1.1

opensuse advisories openSUSE-SU-2024:10235-1

Is CVE-2010-2074 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2010-2074 updated cvss 2.6

w3m: doesn't handle NULL in Common Name properly

  • Red Hat Enterprise Linux (v. 5 server) w3m 0.5.1-17.el5_5, w3m-img 0.5.1-17.el5_5 Red Hat Enterprise Linux Desktop (v. 5 client) w3m 0.5.1-17.el5_5, w3m-img 0.5.1-17.el5_5
    fixed: vendor fix RHSA-2010:0565
  • Red Hat Enterprise Linux 6 w3m, w3m-img
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.49% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.