Open janstarke opened 1 month ago
Unfortunately, it is not possible to provide the data which causes this behaviour
can you provide debug information instead?
All I have is the error message:
Error: c-libesedb: libesedb_table_get_number_of_records: unable to retrieve number of leaf values from table page tree.
libesedb_page_tree_get_number_of_leaf_values: invalid number of leaf pages value exceeds maximum.
libesedb_table_get_number_of_records: unable to retrieve number of leaf values from table page tree.
@Darkrael, you have the test data. Could you please provide some more information to @joachimmetz to help him finding the issue?
Regards, Jan
Also what is c-libesedb
? That seems to be generating the warning.
you have the test data. Could you please provide some more information to @joachimmetz to help him finding the issue?
If no such data can be provided this issue cannot be addressed and feel free to close the issue.
Also what is
c-libesedb
? That seems to be generating the warning.
this is simply a static string in rust-libesedb
:
rust-libesedb
itself is a rust binding for libesedb
However, I agree that the issue should be closed if we don't get more information to debug the issue
Unfortunately, it is not possible to provide the data which causes this behaviour
can you provide debug information instead?
Hey, are you talking about these building flags: https://github.com/libyal/libesedb/wiki/Building#verbose-and-debug-output? If so i can try them. I will get back to you in the coming week when i find the time
@joachimmetz I've sent you an e-mail to the mail in your profile with some debug files. I hope it helps
I'm currently handling a PR for a mitigation of said problem: janstarke/ntdsextract2#16
There seems to be a situation in which the first call to
libesedb_record_get_number_of_values()
fails, while a subsequent call to the same function succeeds. Can you imagine a situation in which this might happen?Unfortunately, it is not possible to provide the data which causes this behaviour :cry: