Can someone tell me which firmware they were using the use after free?
Pretty sure it can be reused to gain kernel code execution.
I'm gonna guess they mitigated it the same as everyone else did....(which can be handled)
I want to take a solid go at it but am feeling too lazy right now to search for it....(in 45 minutes or so I guess I'll go looking for it myself)
(this is not an April fools prank......reason there is no "guarantee of exploit" Just a question I guess I am too lazy to find the answer myself)
Use after free by the way overflows a usage field to force it to wrap back to 0.
It causes the kernel to leak and frees the object. (blah blah blah google it if you don't already know how it is used)
Anyway it is mitigated but very poorly, as in we can get around the mitigation.
This is where it may get fun.....(don't worry MN1 we will credit you for the initial exploit we just wanna reuse some of it.....That is if anything comes of it...)
Pretty sure it can be reused to gain kernel code execution.
I'm gonna guess they mitigated it the same as everyone else did....(which can be handled)
I want to take a solid go at it but am feeling too lazy right now to search for it....(in 45 minutes or so I guess I'll go looking for it myself)
(this is not an April fools prank......reason there is no "guarantee of exploit" Just a question I guess I am too lazy to find the answer myself)
Use after free by the way overflows a usage field to force it to wrap back to 0.
It causes the kernel to leak and frees the object. (blah blah blah google it if you don't already know how it is used)
Anyway it is mitigated but very poorly, as in we can get around the mitigation.
This is where it may get fun.....(don't worry MN1 we will credit you for the initial exploit we just wanna reuse some of it.....That is if anything comes of it...)