New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple OOB reads #43
Comments
|
Thx for the report but know this project is pre-alpha status |
|
Also this project does not support any network communication so your impact assessment needs some adjustments. |
|
Regarding filing cves for this, read libyal/libevt#5. And make sure your report is accurate otherwise it's a waste of people's time and resources.. |
BTW could you send me actual proof of these claims about actual crashes such as core files, which compiler / platform the binary was built. |
|
None of your POC files crash, they are not even accepted as valid input And the same for the other poc files: So this would not lead to any hypothetical denial of service since your file would not be accepted as valid input in the first place. |
|
@seeutonight friendly ping are you going to provide proof to back your claims of your impact assessment? |
|
Marking as:
|
|
No updates from reporter closing issue. |
1.the libesedb_page_read_values function in libesedb_page.c in libesedb allow remote attackers to cause a denial of service(invalid memory read and application crash) via a crafted esedb file.
2.the libesedb_page_read_tags function in libesedb_page.c in libesedb allow remote attackers to cause a denial of service(invalid memory read and application crash) via a crafted esedb file.
3.the libesedb_catalog_definition_read function in libesedb_catalog_definition.c in libesedb allow remote attackers to cause a denial of service(invalid memory read and application crash) via a crafted esedb file.
4.the libesedb_key_append_data function in libesedb_key.c in libesedb allow remote attackers to cause a denial of service(invalid memory read and application crash) via a crafted esedb file.
pocs.zip
The text was updated successfully, but these errors were encountered: