VDB

CVE-2018-19626

CVE-2018-19626 PUBLISHED

Reported by mitre · Published November 29, 2018

In Wireshark 2.6.0 to 2.6.4 and 2.4.0 to 2.4.10, the DCOM dissector could crash. This was addressed in epan/dissectors/packet-dcom.c by adding '\0' termination.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
wiresharkAlpine2.6.5-r0, 2.4.11-r0
wireshark-cliArch Linux2.6.5-1
wiresharkUbuntu:14.04:LTS2.6.5-1~ubuntu14.04.1
wiresharkUbuntu:18.04:LTS2.6.5-1~ubuntu18.04.0
wiresharkwireshark2.6.4, 2.4.10
wiresharkUbuntu:16.04:LTS2.6.5-1~ubuntu16.04.0

Affected products

VendorProductVersions
n/an/an/a
alpinewireshark0, 0
archwireshark-cli0
n/an/a*

Timeline

  • Nov 29, 2018 CVE Published
  • Apr 14, 2021 EPSS Score (30 in total, the first dated here)
  • Jun 1, 2026 Security Advisory (4 in total, the first dated here)
  • Aug 9, 2026 Distribution Patch
  • Sep 20, 2026 CVE Updated
  • Sep 22, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2018-19626
vulnetix vdb fixes CVE-2018-19626

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2018-19626/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›