dbcve.org
WiresharkApplication

CVE-2016-4081

MEDIUM · 5.9 CVSS v3.0 Published 2016-04-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
epan/dissectors/packet-iax2.c in the IAX2 dissector in Wireshark 1.12.x before 1.12.11 and 2.0.x before 2.0.3 uses an incorrect integer data type, which allows remote attackers to cause a denial of service (infinite loop) via a crafted packet.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The IAX2 dissector in Wireshark (packet-iax2.c) contains an incorrect integer data type usage that can trigger an infinite loop when processing a crafted IAX2 packet, causing denial of service.

MitigationUpgrade Wireshark to version 1.12.11/2.0.3 or later, or avoid opening untrusted packet capture files with the IAX2 dissector.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WiresharkApplication
Affected:= 1.12.0= 1.12.1= 1.12.2= 1.12.3= 1.12.4= 1.12.5= 1.12.6= 1.12.7= 1.12.8= 1.12.9= 1.12.10= 2.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Wireshark version
    Run 'wireshark --version' or 'tshark --version' from command line
    Affected if Version is 1.12.0 through 1.12.10, or version 2.0.0 exactly
  2. Verify IAX2 dissector is present
    Open Wireshark GUI, go to Help > About Wireshark > Plugins, or run 'tshark -G dissectors' and search for 'iax2'
    Affected if IAX2 dissector (packet-iax2) is loaded in the installation
  3. Confirm IAX2 protocol is being parsed
    Open a packet capture file (pcap) containing IAX2 traffic, or monitor live traffic with Wireshark/tshark using filter 'iax2'
    Affected if IAX2 packets are displayed or parsed by the dissector

If Wireshark version is 1.12.0-1.12.10 or 2.0.0 AND the IAX2 dissector processes crafted IAX2 packets, the infinite loop vulnerability is triggered.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Wireshark to version 1.12.11/2.0.3 or later, or avoid opening untrusted packet capture files with the IAX2 dissector.

Fix this in Wireshark Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-4081 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-4081 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data