You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Crashing inputs were discovered while fuzzing the go-graphsync DecodeMetadata function. Some of these trace back to go-ipld-prime as you can see in the example below.
Mitigation
I've opened a PR here that prevents these inputs from crashing but am unsure as to what the specific correct behavior of the code is at that point.
Concern
It seems to me that if you can get a graphsync exchange to process responses on a graphsync message where the metadata extension's data is this input, it will crash the goroutine containing the DecodeMetadata call. As far as I can tell, graphsync exchanges are processing responses on incoming messages by default.
Context
Crashing inputs were discovered while fuzzing the go-graphsync
DecodeMetadata
function. Some of these trace back to go-ipld-prime as you can see in the example below.Mitigation
I've opened a PR here that prevents these inputs from crashing but am unsure as to what the specific correct behavior of the code is at that point.
Concern
It seems to me that if you can get a graphsync exchange to process responses on a graphsync message where the metadata extension's data is this input, it will crash the goroutine containing the
DecodeMetadata
call. As far as I can tell, graphsync exchanges are processing responses on incoming messages by default.Crasher
Quoted Input
Output
The text was updated successfully, but these errors were encountered: