As you can see, the field names are obviously lost, together with some high-level details such as:
- whether a varint uses zig-zag encoding or not (will assume no zig-zag by default)
- whether a 32-bit/64-bit value is an integer or float (both shown by default)
- signedness (auto-detect by default)
It shows the fields just in the order they are encoded in the wire, so it can be useful for those wanting to get familiar with the wire format or parser developers, in addition to reverse-engineering.
No dependencies required. Just run
main.pyand feed the protobuf blob on stdin:
After reading the first (blind) analysis of the blob, you typically start defining some of the fields so protobuf-inspector can better parse your blobs, until you get to a point where you have a full protobuf definition and the parser no longer has to guess anything.
./main.py < my-protobuf-blob
Read about defining fields here.
If a parsing error is found, parsing will stop within that field, but will go on unaffected at the outside of the hierarchy. The stack trace will be printed where the field contents would go, along with a hexdump indicating where parsing was stopped in that chunk, if applicable.
So, if you specified a
uint32and a larger varint is found, you'd get something like:
If you specified that some field contained an embedded message, but invalid data was found there, you'd get:
Please note that
main.pywill exit with non-zero status if one or more parsing errors occurred.
There are some tricks you can use to save time when approaching a blob:
- If you are positive that a varint does not use zig-zag encoding, but are still not sure of the signedness, leave it as
varint. If it does use zig-zag encoding, use
sint64unless you are sure it's 32-bit and not 64-bit.
- If a chunk is wrongly being recognized as a
packed chunkor an embedded message, or if you see something weird with the parsed message and want to see the raw bytes, specify a type of
bytes. Conversely, if for some reason it's not being detected as an embedded message and it should, force it to
messageto see the reason.
- If you want to extract a chunk's raw data to a file to analyze it better, specify a type of
dumpand protobuf-inspector will create
dump.1, etc. every time it finds a matching blob.
- protobuf-inspector parses the blob as a message of type
root, but that's just a default. If you have lots of message types defined, you can pass a type name as optional argument, and protobuf-inspector will use that instead of
./main.py request < my-protobuf-blob