This issue is a heap-related error similar to https://github.com/extramaster/bchunk/issues/2 but when replicated using gdb exploitable, it has a hash value that is different. There were 10 different payloads that produces the same hash value as https://github.com/extramaster/bchunk/issues/2 but only 1 other payload produces the following hash value, which makes it evident that this heap-related error is caused by a different part of the code.
(gdb) exploitable
__main__:99: UserWarning: GDB v7.11 may not support required Python API
Description: Heap error
Short description: HeapError (10/22)
Hash: dee2679e6e5af60ee000eb3acd6a6521.9ed6687229c36ed4f3b6957d8de6f879
Exploitability Classification: EXPLOITABLE
Explanation: The target's backtrace indicates that libc has detected a heap error or that the target was executing a heap function when it stopped. This could be due to heap corruption, passing a bad pointer to a heap function such as free(), etc. Since heap errors might include buffer overflows, use-after-free situations, etc. they are generally considered exploitable.
Other tags: AbortSignal (20/22)
(gdb) exploitable
__main__:99: UserWarning: GDB v7.11 may not support required Python API
Description: Heap error
Short description: HeapError (10/22)
Hash: 7dabe720a577c556f3502bc14a09e494.5f6e27cabe9c5ab0e08ffc984674d095
Exploitability Classification: EXPLOITABLE
Explanation: The target's backtrace indicates that libc has detected a heap error or that the target was executing a heap function when it stopped. This could be due to heap corruption, passing a bad pointer to a heap function such as free(), etc. Since heap errors might include buffer overflows, use-after-free situations, etc. they are generally considered exploitable.
Other tags: AbortSignal (20/22)
As mentioned earlier, this is related to #2 but has a different (gdb exploitable) hash value compared to many other payloads. It should be fixed along with the commit that fixed #2 and #4.
Just to be sure, please try the following payload for verification as well: poc.zip
This issue is a heap-related error similar to https://github.com/extramaster/bchunk/issues/2 but when replicated using gdb exploitable, it has a hash value that is different. There were 10 different payloads that produces the same hash value as https://github.com/extramaster/bchunk/issues/2 but only 1 other payload produces the following hash value, which makes it evident that this heap-related error is caused by a different part of the code.
The following is the stack trace output from gdb:
The text was updated successfully, but these errors were encountered: