Hacking Hykem's 5.5 iosu Exploit

[Don Jon]

What they try to patch is the random arbitrary code exec on kernel, not in userland, they moved the way browser manage the memory malloc() and adjust the vbuffering, but they forgot to remove the ERROR, so, this is WHY when it push back to the memory alloc() over the limit, the ERROR give back to exec() at the MP4... so, they ARE STUPID. Also the lib on mp4 should be packed in the new fw, so, someone let it PROPOSITAL inside 5.5.1 to test the hackers to check WHERE TO LOAD and not to GUESS where it is!

On the memory there is a table for, read, load, exec, exec as R, exec as U, so, they let EXEC U and not Exec R....

This mean now nintendo already know how "they" are doing exec on the kernel side, but they DO NOT KNOW how the HACKERS find where to RUN the code (doenst matter signed or not signed) what's matter is HOW THEY FOUND OUT WHERE THE EXEC POSITION ON KERNEL FLUSH IS KNOW!

Hahaha... someone has a nintendo debug unit out of the nintendo shelf... or they had the IOSU debug on hands.... do you know ICE nintendo???

In other words:
they know what kernel exploits we have
tried to patch them
and failed
that is why something will be leaked
somebody call a plumber,
fuck ive said too much

 

[Filzek]

NOOOOOOO...

They know the EXPLOIT..

They DONT know how hackers can TRACE where the malloc() can execute as ROOT...

They KNOW how to hacker can execute as USER.

They HAVENT patched the FW in HOPE the code for LDR LEAK to patch...

hahahahaha

 

[AboodXD]

Too bad Nin, your last action was the best in history...!!
You patched some instable exploits while you fooled people so they can give us stable ones to play with!!
*Laughs so hard*[emoji23] [emoji23]

 

[tivu100]

NOOOOOOO...

They know the EXPLOIT..

They DONT know how hackers can TRACE where the malloc() can execute as ROOT...

They KNOW how to hacker can execute as USER.

They HAVENT patched the FW in HOPE the code for LDR LEAK to patch...

hahahahaha

So basically, the homebrew developers know the trap thus holding on the private kernel exploit right? Cat and mouse game

 

[justinjustin7]

Here:
https://dl.dropboxusercontent.com/u/61808767/WiiU/index.html

Works for me, 5.5.0U, other links don't work.

Thanks, works perfectly!

 

[Bkool999]

Too bad Nin, your last action was the best in history...!!
You thought you patched so exploits while you fooled people so they can give us something to play with!!
*Laughs so hard*[emoji23] [emoji23]

It's so beautiful!!

 

[Onion_Knight]

Too bad Nin, your last action was the best in history...!!
You patched some instable exploits while you fooled people so they can give us stable ones to play with!!
*Laughs so hard*[emoji23] [emoji23]

?
this makes no sense...

 

[gamer4lif3]

i think its more that this yellow8's exploit was never patched and he mistakenly released his some how lol.

 

[Bkool999]

?
this makes no sense...

Lol, he was saying Nintendo thought they patched some exploits, keeping them safe awhile, while in reality, the "patch" lead to allowing some thought-to-be useless exploits being released. Which means they messed up.

 

[AboodXD]

?
this makes no sense...

Nintendo DID patch some exploits in 5.5.1, but they were the instable exploits. In the same time, they've accidently fooled yellows8 to think that his exploit was patched(luckly, that exploit is super stable), and it's out for all of us to enjoy. [emoji14]

Best move by Nin ever!

 

[josh87402]

Nintendo DID patch some exploits in 5.5.1, but they were the instable exploits. In the same time they've accidently fooled yellows8 to think that his exploit was patched(which is super stable), and it's out for all of us to enjoy. [emoji14]

Best move by Nin ever!

Congrats Nintendo!

 

[Don Jon]

NOOOOOOO...

They know the EXPLOIT..

They DONT know how hackers can TRACE where the malloc() can execute as ROOT...

They KNOW how to hacker can execute as USER.

They HAVENT patched the FW in HOPE the code for LDR LEAK to patch...

hahahahaha

Nintendo DID patch some exploits in 5.5.1, but they were the instable exploits. In the same time, they've accidently fooled yellows8 to think that his exploit was patched(luckly, that exploit is super stable), and it's out for all of us to enjoy. [emoji14]

Best move by Nin ever!

which probably means they will patch this Userland exploit by next update

 

[AboodXD]

which probably means they will patch this Userland exploit by next update

But now all 5.5.1 users aren't doomed.

5.5.0=5.5.1, liturally! Same kernel, same IOSU, just the lack of instable webkit exploits that we don't even need. [emoji14]

 

[Filzek]

"Nontendo" did not patch anything, just set a way to findout how HACKERS trace the EXEC in memory without being able to TRACE it. As only USERSPACE are TRACEABLE in the MP4, so no ROOT exec in it.... dingdong... nintendo play it as a BATE

 

[ihateu3]

But now all 5.5.1 users aren't doomed.

5.5.0=5.5.1, liturally! Same kernel, same IOSU, just the lack of instable webkit exploits that we don't even need. [emoji14]

But the people on 5.5.1 will update to 5.5.2 anyways, and then scream about it. We have saw the same scene play out every time an update happens.

 

[AboodXD]

But the people on 5.5.1 will update to 5.5.2 anyways, and then scream about it. We have saw the same scene play out every time an update happens.

Well, I think they have learnt a lesson this time...

 

[OriginalHamster]

Good thing they won't release a new update anytime soon, that give us some more time

 

[Net-KILLER]

Well, I think they have learnt a lesson this time...

Nope. They will never learn.

 

[SonyUSA]

To be fair, Nintendo can only patch what they -know- to be exploited. It was a pre-emptive patch that they had to do blindly because they didn't have the actual exploit to examine. There's no fault in them trying, and now there are 2 less entrypoints for them to worry about.

 

[MAXLEMPIRA]

To be fair, Nintendo can only patch what they -know- to be exploited. It was a pre-emptive patch that they had to do blindly because they didn't have the actual exploit to examine. There's no fault in them trying, and now there are 2 less entrypoints for them to worry about.

maybe that's why they kept the "5.x" and don't made the jump to "6.x"