Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • wireshark wireshark
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 1.4k
    • Issues 1.4k
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 178
    • Merge requests 178
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • External wiki
    • External wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Wireshark FoundationWireshark Foundation
  • wiresharkwireshark
  • Issues
  • #16866
Closed
Open
Issue created Sep 23, 2020 by Jim Borden@borrrdenContributor

BLIP: Static decompression buffer is of insufficient size

Summary

Currently the BLIP dissector uses a statically allocated buffer of 16 Kb in order to store the results of decompressing a compressed message body. However, the 16 Kb figure is the maximum size of a compressed message frame, not an uncompressed one, so any body that has an uncompressed message larger than 16Kb will crash wireshark

Steps to reproduce

The easiest thing to do is to open the attached capture file

What is the current bug behavior?

Wireshark crashes

What is the expected correct behavior?

Wireshark correctly displays the > 16Kb decompressed body

Sample capture file

badtrace.pcapng.gz

Relevant logs and/or screenshots

No relevant logs, the crash is very straightforward

Build information

Version 3.2.6 (v3.2.6-0-g4f9257fb)

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking