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

Challenge: Exploit DirtyCow without /proc/self/mem _and_ without PTRACE_POKE*. #30

Open
dirtycow opened this issue Oct 27, 2016 · 1 comment
Open

Challenge: Exploit DirtyCow without /proc/self/mem _and_ without PTRACE_POKE*. #30

dirtycow opened this issue Oct 27, 2016 · 1 comment
Labels
help wanted

Comments

@dirtycow
Copy link
Owner

From http://seclists.org/oss-sec/2016/q4/246

  1. Exploit DirtyCow without /proc/self/mem and without PTRACE_POKE*.
@MarioPalomaresGallego
Copy link

This is actually the main question i have about this exploit. Why can´t the thread that writes to /proc/self/mem write directly to the address mmap returns.

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

No branches or pull requests
2 participants
@dirtycow @MarioPalomaresGallego