xboxscene.org forums

Pages: 1 ... 15 16 [17]

Author Topic: BugTraq: Xbox360 Hypervisor Vulnerability - Unsigned Code on Kernel 45  (Read 1726 times)

SuRgEx360

  • Archived User
  • Newbie
  • *
  • Posts: 32
BugTraq: Xbox360 Hypervisor Vulnerability - Unsigned Code on Kernel 45
« Reply #240 on: March 08, 2007, 08:41:00 AM »

so there is no other way of knowing if you have a kernal version <4552 without setting up the system?

Logged

Wolves

  • Archived User
  • Sr. Member
  • *
  • Posts: 327
BugTraq: Xbox360 Hypervisor Vulnerability - Unsigned Code on Kernel 45
« Reply #241 on: March 08, 2007, 07:48:00 PM »

QUOTE(zero129 @ Feb 27 2007, 06:25 PM) View Post
Dont worry about kernel versions.
Just take a look at the PSP, Sony tried to stop the exploits lots of times with higher firmwares but people still keep finding new ways to hack the firmware.
I'm sure it will be the same way with this, once the older kernel gets hacked some smart guys will come out with some kinda way to hack newer ones.

Anyway finally this is some great news smile.gif .

Problem being, Microsoft put a little more effort hardware wise into preventing access.  
QUOTE(santa09 @ Feb 27 2007, 07:08 PM) View Post
im not a hacker but from all that i kno. this is pretty much useless unless you have a way to downgrade kernel. Why can you just sniff the key like they did with the original xbox and then inject it into the flash with some code already there so the 360 thinks its signed but it really isnt. mabye?
 
You should keep up to date on the 360's security. That has been basically prevented.
QUOTE(quarky42 @ Feb 27 2007, 07:35 PM) View Post


I agree.  Sure I would *love* to see a modchip come out immediately because of this, but if you were smart enough to come up with a hack like this, then you might also be smart enough to realize that if MicroShaft found you after you blew something like this wide open WITHOUT telling them, they might just sue your right into the ground.  If you told MicroShaft what was up and they ignored you, and then you blew them out of the water with a successful hack they wouldn't have a legal leg to stand on.  You gave them due notice just like the people that discover vulnerabilities in software before evil/bastards find them and get them fixed before they can be exploited...   If the company fails to respond then they publish code.

The other problem with this is that even if you could win in court, MicroShaft has enough money to tie you, your family, your friends, your pets, and your possessions up in legal proceedings until you are old and gray without worrying about any loss to M$.   I give the guy props for covering his ass and releasing all the technical mojo for another skilled hacker to reproduce his results.

Sure downgrade might not be possible at this time with the blown fuse in the processor, but a new bug could hit, or other hackers may discover a way to completely replace the bios ala current xbox modchip style and make it give the same responses to queries ala current drive firmware attacks.   This could be huge in leading towards new hacks.  He just explained how the whole security system handshakes and how it was exploited.  I think that is very worthwhile.  If he was out there to screw the mod community, then he wouldn't have showed anything and bugtraq wouldn't have gotten all those juicy details.


I believe good things will be coming from this.   Even if this exact method doesn't create the end-all-be-all solution, I think it opens many new doors and provides some great insight for minds greater than mine.  I look forward to seeing "what's next".
Amen.
 
QUOTE(eyric101 @ Feb 27 2007, 08:30 PM) View Post
I think what this really means is that the true hackers can now get into the system and hack and learn.  Think about it.  If you are really interested in hacking the 360, you go buy a 360 thats fairly resent of buy one off ebay with that kernal.  Then you get inside via the hack and you find other vulerabilities.
Not really, being 'inside' the 360 wouldn't neccessarily open any new opportunities aside from the one that let you in.










And as much as I hate to say it, it IS possible to develop a hack proof system. This might have been our only way in...
Logged

biga55

  • Archived User
  • Newbie
  • *
  • Posts: 43
BugTraq: Xbox360 Hypervisor Vulnerability - Unsigned Code on Kernel 45
« Reply #242 on: March 08, 2007, 08:35:00 PM »

QUOTE(openxdkman @ Mar 7 2007, 01:43 PM) *

HD_DVD_10-2006.zip xbox kernel 4532 md5:cd4db8e2c94266ab73513c361dd5b8f6
http://www.badongo.com/file/2357641

Thanks man!!!
Logged

TehBanStick

  • Archived User
  • Newbie
  • *
  • Posts: 41
BugTraq: Xbox360 Hypervisor Vulnerability - Unsigned Code on Kernel 45
« Reply #243 on: March 22, 2007, 10:22:00 PM »

Whats with you guys complaining about MS blowing fuses without your permission?
You say what they are doing is illegal, but hacking the kernel and exploiting the system is illegal as well. Stop being hypocrites.
Logged

XHN_SCRAPY

  • Archived User
  • Newbie
  • *
  • Posts: 46
BugTraq: Xbox360 Hypervisor Vulnerability - Unsigned Code on Kernel 45
« Reply #244 on: March 30, 2007, 11:28:00 AM »

Alright now possible to try getting winXP on the xbox360..??? then if it were possible we should name it         "XP-360: (worlds turned.."not really a name")"

homebrew is legal to an extent...

yea the xbox1 and XBOX 360 is Microsofts even if you "own" it. they have patents on it etc etc etc.. the time period in which a patent lasts is average of 14 yrs; so i think, until then the things you buy from any major company or anything with rights and patents is theirs' from what i have been told and  so basically lol i learned in the "worst way possible" lol.   "but i didn't do it lol smile.gif"
Logged

crazyfknheretic

  • Archived User
  • Newbie
  • *
  • Posts: 5
BugTraq: Xbox360 Hypervisor Vulnerability - Unsigned Code on Kernel 45
« Reply #245 on: April 07, 2007, 05:54:00 PM »

QUOTE(Chamrock @ Feb 28 2007, 09:09 PM) View Post

How the f*ck could it be legal to fool you with updates that physically modify your console without permission from the owner? It should be considered as an illegal action as a virus attack. I would cut off the balls from any dude blowing efuses in my console.



ive read this like 15 times in this thread.  and while i have no idea what the fuck you people are talking about xbox1 or 360      i do know that


YOU DO NOT OWN YOUR XBOX   YOU PURCHASED A LISCNESING AGREEMENT FROM MICROSOFT  THEY CAN DO WHATEVER THE FUCK THEY WANT  WITH IT    THEY CAN COME TO YOUR HOUSE AND TAKE IT FROM YOU IF THEY FEEL LIKE IT    


READ THE BOX!!!      

Logged

Hopeful

  • Archived User
  • Sr. Member
  • *
  • Posts: 365
BugTraq: Xbox360 Hypervisor Vulnerability - Unsigned Code on Kernel 45
« Reply #246 on: April 08, 2007, 09:57:00 AM »

QUOTE(Shadow1300 @ Apr 8 2007, 01:34 AM) View Post

I do not think that is true. That is most likely considered stealing. They have a license on the software inside of your 360, but when you buy that license you have complete control over it and you can modify it all you want. XBL is another story though.


And even if it's not *considered* stealing, it truly is. When you buy a 360, morally and rightfully the hardware and anything on it is yours. To alter however you want to. Any law attempting to control this territory is overstepping its rightful boundaries and frankly kind of venturing into dictatorship. To dictate our right to truly buy materials/devices vended at a market is to claim ownership over our very own private household craftsmanship.

Laws claiming that companies can rightfully sell us "a license to use" merchandise sold from commercial stores, without selling us that hardware itself, are frankly bullshit. They're enforceable in the sense that they exist because they can through force. Just because a law can exist through force however, doesn't mean it has a RIGHT to exist.

Text attached to a piece of hardware I buy at a store has NO right to tell me what I just bought and carried out of the store doesn't belong to me. (Or set boundaries on how I can alter it.) What materials you buy and alter in life is an inborn part of each individual, that NO law has the right to claim territory or control over.

However live is a service the xbox only *connects* to, and is actual physical servers on company propery. And because of that we don't have the inborn right to alter it . However no person or law has the right to tell us we can't buy store-vended hardware and alter or copy it however we want to. (As long as we don't sell it.) I realise such laws DO exist. I am saying they have no right to exist and claim control of such things, but do anyway, mainly in the mere name of protecting profit. I've personally always had a huge problem with that.
Logged

NewGuyNeedzHelp

  • Archived User
  • Newbie
  • *
  • Posts: 8
BugTraq: Xbox360 Hypervisor Vulnerability - Unsigned Code on Kernel 45
« Reply #247 on: June 12, 2007, 01:30:00 PM »

i have a japanese system w/ the kernal version 2858, i would assume it would be safe to upgrade it to 4532 and 4548? and since i just heard bout this and have no knowledge of hacking, i guess i'll have to have the box flashed into this proper version?
Logged

mrbelvedere

  • Archived User
  • Jr. Member
  • *
  • Posts: 76
BugTraq: Xbox360 Hypervisor Vulnerability - Unsigned Code on Kernel 45
« Reply #248 on: June 13, 2007, 05:34:00 PM »

I had 2858 then updates to 4532. Worked like a charm. Now I enjoy linux on 1 xbox, and live on another biggrin.gif
Logged
Pages: 1 ... 15 16 [17]