Handle gRPC requests as tainted sources #43
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces support for identifying
google.golang.org/protobuf/proto.Messagetypes as potential sources in taint analysis, particularly for gRPC-based services. It includes updates to the taint analysis logic, new helper functions, and additional test cases across multiple vulnerability categories like log injection and SQL injection.Enhancements to taint analysis:
google.golang.org/protobuf/proto.Messageas a source type in taint analysis for log injection and SQL injection vulnerabilities.checkSSAValuefunction to check if a type implements theProtoMessagemethod, identifying protobuf message types as sources.hasProtoMessageMethodhelper function to determine if a type implements theProtoMessagemethod.Miscellaneous updates:
go/typesimport to support type-checking logic forProtoMessagemethod detection.https://chatgpt.com/codex/tasks/task_e_686bf2bc49988331aedaf649cb8f59cd