Linux local root exploit for CVE-2014-0038
1–10 of 36 posts
Re: Linux local root exploit for CVE-2014-0038
#2If it's non-universal, why is it? E.g. if it only affects Ubuntu, then what is it about Ubuntu that allows this to work?
EDIT: This seems to be the answer: https://news.ycombinator.com/item?id=7154922 ... Any distro using the x32 ABI is vulnerable, and Ubuntu just recently enabled the x32 ABI.
Re: Linux local root exploit for CVE-2014-0038
#3Re: Linux local root exploit for CVE-2014-0038
#4Which is only used on the(already vastly irresponsibly-constructed) Ubuntu 13.10.
Re: Linux local root exploit for CVE-2014-0038
#5Is this a universal exploit? Which distros are unaffected? If it's non-universal, why is it? E.g. if it only affects Ubuntu, then what is it about Ubuntu that allows this to work? EDIT: This seems to be the answer: https://news.ycombinator.com/item?id=7154922 ... Any distro using the x32 ABI is vulnerable, and Ubuntu just recently enabled the x32 ABI.
Re: Linux local root exploit for CVE-2014-0038
#6Is this a universal exploit? Which distros are unaffected? If it's non-universal, why is it? E.g. if it only affects Ubuntu, then what is it about Ubuntu that allows this to work? EDIT: This seems to be the answer: https://news.ycombinator.com/item?id=7154922 ... Any distro using the x32 ABI is vulnerable, and Ubuntu just recently enabled the x32 ABI.
Edit: turns out that 13.10 is released with the CONFIG_X86_X32 option enabled, just the usual negligent excessive differentiation that Canonical loves to impose on its customers(see Mir and moving forward with Upstart for recent examples).
Re: Linux local root exploit for CVE-2014-0038
#7Is this a universal exploit? Which distros are unaffected? If it's non-universal, why is it? E.g. if it only affects Ubuntu, then what is it about Ubuntu that allows this to work? EDIT: This seems to be the answer: https://news.ycombinator.com/item?id=7154922 ... Any distro using the x32 ABI is vulnerable, and Ubuntu just recently enabled the x32 ABI.
Essentially, if this option is enabled, someone can use the linked code to exploit an x32 syscall and escalate privileges.
Ubuntu specifically is a target because they recently enabled this option; I'm not aware of any other distros that have done so.
Re: Linux local root exploit for CVE-2014-0038
#8You should clarify that it only applies to the x32 ABI. Which is only used on the(already vastly irresponsibly-constructed) Ubuntu 13.10.
Re: Linux local root exploit for CVE-2014-0038
#9You should clarify that it only applies to the x32 ABI. Which is only used on the(already vastly irresponsibly-constructed) Ubuntu 13.10.
Re: Linux local root exploit for CVE-2014-0038
#10 #define PAYLOADSIZE 0x2000
code += PAYLOADSIZE - 1024;
memcpy((void*)code, &kernel_payload, 1024);
Does anybody know if it's possible to find out the size of a function during run time? Could you like say, put a return at the end of the function then do a for-loop with memcpy() for each byte until you run into the OPCODE for RET? I guess I could do a test.