paritytech/parity-db

Corrupted btree entries should not result in panics

Closed this issue · 1 comments

When parsing value table entries all expected reads should be validated agains actual buffer size. I believe regular hash value table already have checks in place. Btree entry parsing however does not and should be fixed.

Example of such panic: #190

cheme commented

Right, will check this part (sounds like a nice monday morning task :)