Every CVE Search/ Get API key

CVE-2016-9621

Security update for w3m

No scoreRejected

DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2016-9429. Reason: This candidate is a reservation duplicate of CVE-2016-9429. Notes: All CVE users should reference CVE-2016-9429 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage

What each source reports

CVE List No score

DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2016-9429. Reason: This candidate is a reservation duplicate of CVE-2016-9429. Notes: All CVE users should reference CVE-2016-9429 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage

Record
CVE-2016-9621
Updated
2026-11-02
EUVDEUVD-2016-10423 No score

DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2016-9429. Reason: This candidate is a reservation duplicate of CVE-2016-9429. Notes: All CVE users should reference CVE-2016-9429 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage

Record
EUVD-2016-10423
Updated
2026-11-03
NVD No score

Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2016-9429. Reason: This candidate is a reservation duplicate of CVE-2016-9429. Notes: All CVE users should reference CVE-2016-9429 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage

Record
CVE-2016-9621
Updated
2026-11-02
OSVopenSUSE-SU-2024:10235-1 No score

w3m-0.5.3.git20161120-1.1 on GA media

These are all security issues fixed in the w3m-0.5.3.git20161120-1.1 package on the GA media of openSUSE Tumbleweed.

Record
openSUSE-SU-2024:10235-1
Updated
2026-11-02
OSVSUSE-SU-2016:3046-1 No score

Security update for w3m

This update for w3m fixes the following issues:

  • update to debian git version (bsc#1011293) addressed security issues: CVE-2016-9621: w3m: global-buffer-overflow write (bsc#1012020) CVE-2016-9622: w3m: null deref (bsc#1012021) CVE-2016-9623: w3m: null deref (bsc#1012022) CVE-2016-9624: w3m: near-null deref (bsc#1012023) CVE-2016-9625: w3m: stack overflow (bsc#1012024) CVE-2016-9626: w3m: stack overflow (bsc#1012025) CVE-2016-9627: w3m: heap overflow read + deref (bsc#1012026) CVE-2016-9628: w3m: null deref (bsc#1012027) CVE-2016-9629: w3m: null deref (bsc#1012028) CVE-2016-9630: w3m: global-buffer-overflow read (bsc#1012029) CVE-2016-9631: w3m: null deref (bsc#1012030) CVE-2016-9632: w3m: global-buffer-overflow read (bsc#1012031) CVE-2016-9633: w3m: OOM (bsc#1012032) CVE-2016-9434: w3m: null deref (bsc#1011283) CVE-2016-9435: w3m: use uninit value (bsc#1011284) CVE-2016-9436: w3m: use uninit value (bsc#1011285) CVE-2016-9437: w3m: write to rodata (bsc#1011286) CVE-2016-9438: w3m: null deref (bsc#1011287) CVE-2016-9439: w3m: stack overflow (bsc#1011288) CVE-2016-9440: w3m: near-null deref (bsc#1011289) CVE-2016-9441: w3m: near-null deref (bsc#1011290) CVE-2016-9442: w3m: potential heap buffer corruption (bsc#1011291) CVE-2016-9443: w3m: null deref (bsc#1011292)
Record
SUSE-SU-2016:3046-1
Updated
2026-11-02
OSVSUSE-SU-2016:3053-1 No score

Security update for w3m

This update for w3m fixes the following issues:

  • update to debian git version (bsc#1011293) addressed security issues: CVE-2016-9622: w3m: null deref (bsc#1012021) CVE-2016-9623: w3m: null deref (bsc#1012022) CVE-2016-9624: w3m: near-null deref (bsc#1012023) CVE-2016-9625: w3m: stack overflow (bsc#1012024) CVE-2016-9626: w3m: stack overflow (bsc#1012025) CVE-2016-9627: w3m: heap overflow read + deref (bsc#1012026) CVE-2016-9628: w3m: null deref (bsc#1012027) CVE-2016-9629: w3m: null deref (bsc#1012028) CVE-2016-9630: w3m: global-buffer-overflow read (bsc#1012029) CVE-2016-9631: w3m: null deref (bsc#1012030) CVE-2016-9632: w3m: global-buffer-overflow read (bsc#1012031) CVE-2016-9633: w3m: OOM (bsc#1012032) CVE-2016-9434: w3m: null deref (bsc#1011283) CVE-2016-9435: w3m: use uninit value (bsc#1011284) CVE-2016-9436: w3m: use uninit value (bsc#1011285) CVE-2016-9437: w3m: write to rodata (bsc#1011286) CVE-2016-9438: w3m: null deref (bsc#1011287) CVE-2016-9439: w3m: stack overflow (bsc#1011288) CVE-2016-9440: w3m: near-null deref (bsc#1011289) CVE-2016-9441: w3m: near-null deref (bsc#1011290) CVE-2016-9442: w3m: potential heap buffer corruption (bsc#1011291) CVE-2016-9443: w3m: null deref (bsc#1011292)
Record
SUSE-SU-2016:3053-1
Updated
2026-11-02

Affected packages

Affected packages
PackageAffectedFixed
w3m
SUSE:Linux Enterprise Server 11 SP4
From an advisory covering 28 CVEs
before 0.5.3.git20161120-4.1
0.5.3.git20161120-4.1
w3m
SUSE:Linux Enterprise Server for SAP Applications 11 SP4
From an advisory covering 28 CVEs
before 0.5.3.git20161120-4.1
0.5.3.git20161120-4.1
w3m
SUSE:Linux Enterprise Desktop 12 SP1
From an advisory covering 23 CVEs
before 0.5.3.git20161120-160.1
0.5.3.git20161120-160.1
w3m
SUSE:Linux Enterprise Desktop 12 SP2
From an advisory covering 23 CVEs
before 0.5.3.git20161120-160.1
0.5.3.git20161120-160.1
w3m
SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2
From an advisory covering 23 CVEs
before 0.5.3.git20161120-160.1
0.5.3.git20161120-160.1
w3m
SUSE:Linux Enterprise Server 12 SP1
From an advisory covering 23 CVEs
before 0.5.3.git20161120-160.1
0.5.3.git20161120-160.1
w3m
SUSE:Linux Enterprise Server for SAP Applications 12 SP1
From an advisory covering 23 CVEs
before 0.5.3.git20161120-160.1
0.5.3.git20161120-160.1
w3m
SUSE:Linux Enterprise Server 12 SP2
From an advisory covering 23 CVEs
before 0.5.3.git20161120-160.1
0.5.3.git20161120-160.1
w3m
SUSE:Linux Enterprise Server for SAP Applications 12 SP2
From an advisory covering 23 CVEs
before 0.5.3.git20161120-160.1
0.5.3.git20161120-160.1
w3m
openSUSE:Tumbleweed
From an advisory covering 25 CVEs
before 0.5.3.git20161120-1.1
0.5.3.git20161120-1.1

History

History
RecordedChangedSources
affected, facts
aliasesEUVD
first indexedCVE List, NVD, OSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

CVE-2016-9621 has been rejected by its source and should not be treated as a live vulnerability, published November 25, 2016.

References

Show 53 moreShow less
MoveEnter Open