Skip to content
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

Verification fails due to #4

Open
vykt opened this issue May 17, 2024 · 1 comment
Open

Verification fails due to #4

vykt opened this issue May 17, 2024 · 1 comment
Assignees
Labels
bug Something isn't working inprog Reviewing

Comments

@vykt
Copy link
Owner

vykt commented May 17, 2024

Affected versions: v0.1.0+

Pointer chain verification fails because memory segments without backing files ('pathname' field in 'man 5 proc') derive their name from their starting address. Because of ASLR, across execution instances these names become invalid, leading to error in interpreting and verifying saved scans.

This bug was introduced in v0.1.0, which changed the names of backing files from '<NO_PATHNAME>' to their starting address, for regions which lack a backing file.

The solution is probably to treat such segments as belonging to the closest previous segment with a backing file. This approach will detect pointer chains where a pointer chain arrives to a segment that consistently follows some shared object.

@vykt vykt added bug Something isn't working inprog Reviewing labels May 17, 2024
@vykt vykt self-assigned this May 17, 2024
@vykt
Copy link
Owner Author

vykt commented May 17, 2024

Updating libpwu to allow for this behaviour.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working inprog Reviewing
Projects
None yet
Development

No branches or pull requests

1 participant