|
2016-10-24
, 05:35
|
Posts: 1,293 |
Thanked: 4,319 times |
Joined on Oct 2014
|
#13
|
The Following 3 Users Say Thank You to nieldk For This Useful Post: | ||
|
2016-10-24
, 07:54
|
|
Posts: 1,583 |
Thanked: 1,203 times |
Joined on Dec 2011
@ Everywhere
|
#14
|
|
2016-10-24
, 09:16
|
|
Posts: 1,196 |
Thanked: 2,708 times |
Joined on Jan 2010
@ Hanoi
|
#16
|
Well, it looks like kernel 3.10 and later are the "easy to exploit" so it sounds like we might be semi-safe on Maemo. Still worrysome.
I have yet to try this on my android phone, then again I don't use my android phone that much.
In any case you don't need permissions to run the dirty cow exploit, it's just regular code (but it looks like you may need multithreading enabled as well as being able to write to your own address space through /proc.)
In android I wish it were possible to fine grain control all the functions that they say on those "XYZ needs access to ABC"...
Just let them install, but the user gets to control whether XYZ actually gets to use feature ABC.
Even better, return garbage information.
Now that's what I wish could be done.
The Following User Says Thank You to ste-phan For This Useful Post: | ||
|
2016-10-24
, 10:02
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#17
|
In case you want to experiment, this PoC can help identify if vulnerable.
https://github.com/dirtycow/dirtycow...ter/dirtyc0w.c
|
2016-10-24
, 10:26
|
|
Posts: 6,436 |
Thanked: 12,701 times |
Joined on Nov 2011
@ Ängelholm, Sweden
|
#18
|
|
2016-10-24
, 18:39
|
|
Posts: 1,338 |
Thanked: 1,055 times |
Joined on Oct 2009
@ California, USA / Jordan
|
#19
|
I have yet to try this on my android phone, then again I don't use my android phone that much.
In any case you don't need permissions to run the dirty cow exploit, it's just regular code (but it looks like you may need multithreading enabled as well as being able to write to your own address space through /proc.)
In android I wish it were possible to fine grain control all the functions that they say on those "XYZ needs access to ABC"...
Just let them install, but the user gets to control whether XYZ actually gets to use feature ABC.
Even better, return garbage information.
Now that's what I wish could be done.