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,349
    • Issues 1,349
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 178
    • Merge requests 178
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • 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
  • #18730
Closed
Open
Issue created Dec 12, 2022 by Gaetano Giunta@gggeek

Crash when analyzing protobuf packets

Summary

Wireshark crashed as soon as opening a pcap file containing 2 protobuf packets

Steps to reproduce

  • load attached .proto file (set WS to load it on startup)
  • set default protobuf decoding for port 30002 to 'Request'
  • open attached .pcap file

What is the current bug behavior?

windows open with error message " ** (wireshark:9132) 16:17:27.284818 [WSUtil ERROR] C:\gitlab-builds\builds\MsQ3pox2\0\wireshark\wireshark\wsutil\json_dumper.c:160 -- json_dumper_bad(): Bad json_dumper state: illegal transition; change=1 type=2 depth=1 prev/curr/next state=0a 01 04"

What is the expected correct behavior?

no crashing, 2 protobuf messages parsed

Files attached:

packets.cap pinba.proto

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