doyensec/protoburp

Updated version of the ProtoBurp Extension, with enhanced features and capabilities to encode and fuzz custom protobuf messages

protoburp's Issues

Introduce a Wiki for Extended Documentation

Set up a Wiki that provides information on how to execute certain tasks. This will ensure the README.MD file isn't excessively long.

Investigate Protoc Deserialization and Re-serialization Without Definitions

Research the capability of protoc to deserialize data without its original definition and whether it's possible to re-serialize it. Familiarize oneself with the documentation for clarity.

Support for Compression/Decompression

Implement support for data compression and decompression

Support for WebSockets

Any plans to add support for decoding/encoding protobufs in websockets messages?

protobuf-encoder is not selecting the correct message

protoburp/protobuf-encoder.py

Line 71 in 691ec00

for name, obj in inspect.getmembers(proto_module):

This line is only returning the first Message in alphabetical order. This results in the following error if that's not the correct message:

Subprocess exited with error (status code 1):
Traceback (most recent call last):
  File "/Library/Python/3.9/lib/python/site-packages/google/protobuf/json_format.py", line 554, in _ConvertFieldValuePair
    raise ParseError(
google.protobuf.json_format.ParseError: Message type "com.saasbee.pbx.proto.MyMessage" has no field named "mySubMessage" at "MyMessage".
 Available Fields(except extensions): "['field1', 'field2', 'field3', 'field4', 'field5']"

Utilization of Descriptor Over Python Output

Look into the feasibility and advantages of using only the descriptor instead of the generated Python output.

Refactor Codebase Structure

Break down the codebase into organized directories. Consider introducing more modules, striving to keep related functionalities as separated as possible, such as UI, Interceptor, Bridge, Encoding, and Decoding.