dbcve.org
Debian LinuxOperating system · Debian

CVE-2013-4077

MEDIUM · 5.0 CVSS v2.0 Published 2013-06-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/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
Array index error in the NBAP dissector in Wireshark 1.8.x before 1.8.8 allows remote attackers to cause a denial of service (application crash) via a crafted packet, related to nbap.cnf and packet-nbap.c.

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

Array index error in Wireshark's NBAP protocol dissector allows crafted packets to cause a denial of service via application crash. The vulnerability stems from improper bounds checking in packet-nbap.c when processing malformed NBAP packets.

MitigationUpgrade Wireshark to version 1.8.8 or later. Until then, avoid opening untrusted packet capture files from unknown sources.

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
Debian LinuxOperating system
Affected:= 7.0
WiresharkApplication
Affected:= 1.8.0= 1.8.1= 1.8.2= 1.8.3= 1.8.4= 1.8.5= 1.8.6= 1.8.7
OpensuseOperating system
Affected:= 11.4= 12.2= 12.3

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
Low
Authentication
None
Confidentiality
None
Integrity
None
Availability
Partial

AV:N/AC:L/Au:N/C:N/I:N/A:P

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. Verify Wireshark is installed
    Run `dpkg -l wireshark` on Debian/Ubuntu, `rpm -qa wireshark` on RHEL/SUSE, or `wireshark --version` to see the installed version
    Affected if Wireshark is not installed on the system
  2. Determine installed Wireshark version
    Run `wireshark --version` or check via package manager. The output shows the version number (e.g., 1.8.5)
    Affected if The version is 1.8.0, 1.8.1, 1.8.2, 1.8.3, 1.8.4, 1.8.5, 1.8.6, or 1.8.7
  3. Confirm NBAP protocol dissector is present
    Wireshark ships with dissectors in the installation directory. The NBAP dissector is in packet-nbap.c. Check if Wireshark recognizes NBAP by opening a capture file or running `tshark -G protocols | grep -i nbap`
    Affected if NBAP dissector is available in the Wireshark installation and the application can process NBAP traffic
  4. Identify if NBAP traffic or capture files are being analyzed
    Review packet capture files or live captures for NBAP protocol usage. Look for NBAP in the Protocol column in the Wireshark GUI or use `tshark -r capture.pcap -Y nbap` to filter for NBAP packets
    Affected if NBAP packets are being dissected or capture files containing NBAP traffic are opened

You are affected if Wireshark version 1.8.0 through 1.8.7 is installed and NBAP protocol traffic or capture files are being processed.

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.8.8 or later. Until then, avoid opening untrusted packet capture files from unknown sources.

Fix this in Debian Linux Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-4077 — 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-2013-4077 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