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.

Sign up for GitHub

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

Jump to bottom

The PoC of tcache poisoning no longer work on GLIBC 2.30 and above #117

Closed
Zzorz opened this issue May 6, 2020 · 4 comments
Closed

The PoC of tcache poisoning no longer work on GLIBC 2.30 and above #117

Zzorz opened this issue May 6, 2020 · 4 comments

Comments

@Zzorz
Copy link

Zzorz commented May 6, 2020 •
edited
Loading

The PoC of tcache poisoning no longer work on GLIBC 2.30 and above.
There's a small change in _int_malloc() at https://sourceware.org/git/?p=glibc.git;a=commit;h=77dc0d8643aa99c92bf671352b0a8adde705896f.
@Zzorz Zzorz changed the title Tcache poisoning no longer work on GLIBC 2.30 and above The PoC of tcache poisoning no longer work on GLIBC 2.30 and above May 6, 2020
@Kyle-Kyle
Copy link
Contributor

To fix the tcache poisoning poc. It is pretty simple. I'm going to fix it.
But damn, this breaks some exploitation primitives.

@Kyle-Kyle
Copy link
Contributor

resolved in commit 68fa363

@Kyle-Kyle
Copy link
Contributor

Not sure whether there is any other poc broken because of this patch.
I will leave this issue open until we have done further checks.

@Kyle-Kyle
Copy link
Contributor

after the refactor, everything is clean now. Thanks for the report!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Kyle-Kyle @Zzorz