xboxscene.org forums

Pages: 1 ... 14 15 [16] 17

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

kevhonda

  • Archived User
  • Full Member
  • *
  • Posts: 126
BugTraq: Xbox360 Hypervisor Vulnerability - Unsigned Code on Kernel 45
« Reply #225 on: March 01, 2007, 07:37:00 PM »

QUOTE(Chamrock @ Mar 1 2007, 12:23 PM) *

This is exactly what I mentioned before about the legality of blowing the fuse! Group-sue MS for doing this! No asshole should ever hack into my hardware without my permission! I hope EU will sue MS and demand billion of dollars and give it to the 360 owners. MS need some serious threat so they could stop this shit! I think we have the fully right to blow their property if they blow ours!  grr.gif  muhaha.gif


I've got some property they can BLOW, I'll give you one hint...its not an eFuse smile.gif
Logged

Iriez

  • Administrator
  • Hero Member
  • *****
  • Posts: 1238
BugTraq: Xbox360 Hypervisor Vulnerability - Unsigned Code on Kernel 45
« Reply #226 on: March 01, 2007, 10:39:00 PM »

QUOTE(Chamrock @ Mar 1 2007, 06:23 AM) View Post

This is exactly what I mentioned before about the legality of blowing the fuse! Group-sue MS for doing this! No asshole should ever hack into my hardware without my permission! I hope EU will sue MS and demand billion of dollars and give it to the 360 owners. MS need some serious threat so they could stop this shit! I think we have the fully right to blow their property if they blow ours!  grr.gif  muhaha.gif


Uhm, obviously you dont understand the intellectual property rights here. You officially do not OWN your xbox360. According to the license agreement presented by microsoft, you are in a sense, simply leasing the xbox360, and they own FULL intellectual property of the xbox360, and can make ANY adjustments to it, at ANY time they want.

Hope that settles your rant.
Logged

openxdkman

  • Archived User
  • Hero Member
  • *
  • Posts: 550
BugTraq: Xbox360 Hypervisor Vulnerability - Unsigned Code on Kernel 45
« Reply #227 on: March 01, 2007, 11:52:00 PM »

Legally considered as a leasing... Interesting... I've always thought console business should be true leasing since they want to sell at price that is under real production cost...

True sale : You own it. You should have the right to control the global state of your property (like a car).
True leasing : You just use it. But if a failure happens you should get a free replacement (any time, without any time limit).

I think politics should do something and forbid economic models that are just "floating" between these two models. It's too easy to take profit from first one (you sell and 1 year later if failure happens, consumer has to purchase a new one or pay 70% of total price for a replacement) and claim at same time total property with second model.

Logged

Iriez

  • Administrator
  • Hero Member
  • *****
  • Posts: 1238
BugTraq: Xbox360 Hypervisor Vulnerability - Unsigned Code on Kernel 45
« Reply #228 on: March 02, 2007, 01:45:00 PM »

QUOTE(openxdkman @ Mar 2 2007, 01:52 AM) View Post

Legally considered as a leasing... Interesting... I've always thought console business should be true leasing since they want to sell at price that is under real production cost...

True sale : You own it. You should have the right to control the global state of your property (like a car).
True leasing : You just use it. But if a failure happens you should get a free replacement (any time, without any time limit).

I think politics should do something and forbid economic models that are just "floating" between these two models. It's too easy to take profit from first one (you sell and 1 year later if failure happens, consumer has to purchase a new one or pay 70% of total price for a replacement) and claim at same time total property with second model.


Like i said, 'in a sense'. I did not state you a literally leasing it, but the concept is there.
Logged

Methadon

  • Archived User
  • Full Member
  • *
  • Posts: 149
BugTraq: Xbox360 Hypervisor Vulnerability - Unsigned Code on Kernel 45
« Reply #229 on: March 02, 2007, 08:46:00 PM »

QUOTE(Millenia1x @ Feb 28 2007, 04:15 AM) View Post

but will we be required to downgrade the system to use this

well, this is xbox ALL OVER


Of course:

Xbox = xbox
360 = a full circle (or "all over" again)

QUOTE(NumarkTTX1 @ Feb 28 2007, 06:02 AM) View Post

3 cheers to ms!

HIP HIP HOORAY! HIP HIP HOORAY!

i would love to see hombrew on 360... but as soon as this bad boy is cracked the ban hammer is comin down HARD!


 That's only two cheers tongue.gif

 Anywayz, yes. Just like the original xbox, expect to be banned from XBL if your console is running UNSIGNED CODE. For some reason, the vast majority of people think XBL bans for the X1s was over "your system is modded; you must be a pirate" concept, when if you look from a company standpoint, it's more of a "your system is allowing you to run ANY code, and is unfair to the popular user because it enables you to cheat on the same game that little timmy plays normally" type of concept.

QUOTE(openxdkman @ Feb 28 2007, 10:43 AM) View Post

Mmm, I'm a bit disappointed. I was hoping hacker could wait for release of 65nm model...
Current model lifespan is a bit small for doing interesting things on long term... Whatever...



 Current model lifespan is a bit small? There's over 10.5 million units of the "current model" sold...

QUOTE(t10 @ Feb 28 2007, 01:35 PM) View Post

LMAO, almost every post starts with "I'm no... hacker/cracker/chip designer etc" then adds some dumb suggestion. Talk about redundancy.

Anyhoo props to the original hacker, he is a smart fellah. Too bad for us though he likes money over prison.


 I was thinking the same thing (I could see someone chiming in another post "I'm no pirate..." tongue.gif (BTW, I am in no way condoning piracy, violation of TOS, or any other bullshit before any of you think I am. Read my sig.

As far as the "money over prison" part, I really don't see how hacking the xbox in this manner could land you in jail. If you purchase the Xbox 360™, is it not *yours*? I don't recall signing something at the time of purchase which states that I am leasing said property. I paid cash, and got my system. If I decide I want to crash this 360 (which I legally purchased and own until I relinquesh it by whatever means at whatever time) in order to run whatever I want; I should be allowed. The only thing I could see as being illegal about it is if the means to do it were illegal (ie, you must used a XDK or something that should be unavailable to you, thus making the process involve theft somewhere *note* Stealing is wrong, and not condoned by me or my subsidiaries which I incorrectly spelled tongue.gif ).

QUOTE(mojoman @ Feb 28 2007, 03:14 PM) View Post

You guys are in Denial. How does this help us at all. Somone found a hole and quickly told microshit. If at all anything, what we should be doing is,  insult this traitor, I mean people are painfully looking for ways to crack this thing, and what does he do when he finds this.  He goes straight to the microshits. The guy is a big fool.


 I say you are the fool. Going to MS is in no way that bad a thing. He simply let them know one of their errors, which could actually cause problems (potentially) with a random game, which would lessen certain users' experiences. It's still exploitable with that version, and a blown efuse doesn't mean others can't enjoy it. Perhaps they can crash that version xbox 360 kernel and obtain all kinds of information that will enable them to hack any 360 by other means. Perhaps it will be possible to put one of the kernels on a chip and somehow circumvent the necessity of an efuse. Perhaps something completely different may happen. The keyword here is "perhaps", and as it stands, not telling MS about the flaws in the aforementioned kernels would not gaurantee they wouldn't have fixed it anyway, and also does not mean that the door was slammed in anyones face. It simply means that if you think that, you have a lot more to learn before you bring something to the modding community.

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

How can MS legally release updates that physically blow efuses without approval of the owner? That would be considered as intruding and should be punished to maximum extent, even if we have to bomb MS offices.


 Because TMK, it doesn't physically alter the system. an efuse is an electronic signal similar to a "flag" in the programming realm.

QUOTE(Mike Bowler @ Feb 28 2007, 10:43 PM) View Post

You know i think some people have forgotten that if the original xbox was never hacked then it wouldn't have sold as good as it did so with that in mind i think M$ are playing a game of cat and mouse until the 360 loses appeal then they'll deliberately leave a hole in the last firmware which will allow the 360 to be hacked and homebrew put in place and then they'll come out with a new console which will probably sell like f*ck along with the 360 selling in the background because people want to use homebrew on it.


 Actually I think the original xbox didn't sell as well as they projected because of the severe lack of japanese support compared to any other system. The sales picked up from the modding community because xbox was by far the most modable and customizable console, as it is more or less a pre-packaged PC in a MS-branded case.

QUOTE(Iriez @ Mar 2 2007, 06:46 AM) View Post

Uhm, obviously you dont understand the intellectual property rights here. You officially do not OWN your xbox360. According to the license agreement presented by microsoft, you are in a sense, simply leasing the xbox360, and they own FULL intellectual property of the xbox360, and can make ANY adjustments to it, at ANY time they want.

Hope that settles your rant.


 The license agreement that is never signed and notarized, thus no court could hold it more binding than a verbal agreement with no witnesses.
Logged

sp1200

  • Archived User
  • Jr. Member
  • *
  • Posts: 71
BugTraq: Xbox360 Hypervisor Vulnerability - Unsigned Code on Kernel 45
« Reply #230 on: March 03, 2007, 04:02:00 AM »

Interesting to note what this development says about the DVD firmware hack. MS was quick to update the kernel to plug this hypervisor bug. Their lack of action against the firmware hack suggests to me that they are able to do little if anything to fight it.

Logged

X360 Doktore

  • Archived User
  • Newbie
  • *
  • Posts: 2
BugTraq: Xbox360 Hypervisor Vulnerability - Unsigned Code on Kernel 45
« Reply #231 on: March 03, 2007, 04:23:00 AM »

Hi, I have removed the resistor and updated the 360 to Kernel 4532 and after that I flashed it to 4552 , is there any way to flash it back to 4532 again?

For those who dont know where the resistor is to be found , I made 2 pics where its position can be nicely seen.

http://rs64l3.rapids.../X360MB_2.2.jpg

http://rs65tl2.rapid.../X360MB_1.1.jpg

regards
Logged

Fragreaver

  • Archived User
  • Newbie
  • *
  • Posts: 43
BugTraq: Xbox360 Hypervisor Vulnerability - Unsigned Code on Kernel 45
« Reply #232 on: March 03, 2007, 06:47:00 AM »

Why updated? It's possible to downgrade, but it's not that easy.
Desolder the hynix and reflash it with a external programmer.
And soldering it back to the console of course...

You shouldn't update, if you have the right kernel. :/

This post has been edited by Fragreaver: Mar 3 2007, 02:50 PM
Logged

X360 Doktore

  • Archived User
  • Newbie
  • *
  • Posts: 2
BugTraq: Xbox360 Hypervisor Vulnerability - Unsigned Code on Kernel 45
« Reply #233 on: March 03, 2007, 07:30:00 AM »

Thanks for your answer , I dont have any idea why I did this , I just wanted to test whether its possible to flash it back or not ,  isn´t it possible to change the Kernel update? Because the way you told me of doing it with the desolding is uncomfortable to me!
Logged

Fragreaver

  • Archived User
  • Newbie
  • *
  • Posts: 43
BugTraq: Xbox360 Hypervisor Vulnerability - Unsigned Code on Kernel 45
« Reply #234 on: March 03, 2007, 07:43:00 AM »

Sadly, you can't change the updates. They are encrypted and signed.
If you change only a byte in the update file, the signature is broken and it won't execute.

I guess you'll have to wait for an easier method to downgrade. But you're lucky - your efuse is not 'defective'.
So you'll be able to use any older kernel without a trouble.

This post has been edited by Fragreaver: Mar 3 2007, 03:43 PM
Logged

iquid-!ce

  • Archived User
  • Full Member
  • *
  • Posts: 100
BugTraq: Xbox360 Hypervisor Vulnerability - Unsigned Code on Kernel 45
« Reply #235 on: March 06, 2007, 05:41:00 AM »

Nice to see things are starting to progress and unsigned code running on the 360 could be a possibility soon.
My 360 has been sat under the tv since the january after release day waiting for this day so no dash updates for me!
Maybe my xbox 1 will finally be able to retire from its job as media centre in my house.. poor thing has been hammerd every day for god knows how many years
Logged

biga55

  • Archived User
  • Newbie
  • *
  • Posts: 43
BugTraq: Xbox360 Hypervisor Vulnerability - Unsigned Code on Kernel 45
« Reply #236 on: March 07, 2007, 11:22:00 AM »

The fall update disc that Castor420 linked to is now gone.  Can anyone upload it somewhere?
Logged

openxdkman

  • Archived User
  • Hero Member
  • *
  • Posts: 550
BugTraq: Xbox360 Hypervisor Vulnerability - Unsigned Code on Kernel 45
« Reply #237 on: March 07, 2007, 11:36:00 AM »

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

SuRgEx360

  • Archived User
  • Newbie
  • *
  • Posts: 32
BugTraq: Xbox360 Hypervisor Vulnerability - Unsigned Code on Kernel 45
« Reply #238 on: March 07, 2007, 06:20:00 PM »

if i buy a preimum or core xbox360 in the UK tommorow will it be a kernal version that can be exploited ?
Logged

openxdkman

  • Archived User
  • Hero Member
  • *
  • Posts: 550
BugTraq: Xbox360 Hypervisor Vulnerability - Unsigned Code on Kernel 45
« Reply #239 on: March 08, 2007, 07:35:00 AM »

well... tell the vendor you heard horror stories about not working xbox360's and ask to play the console a few minutes before purchasing it...

and discretly, go check the kernel version in the last right panel.

of course, don't insert any retail game published after mid-january (would upgrade kernel) and don't connect to internet with it

also, don't be too much scared if you discover your drive can't be flashed yet (necessary if you plan to use the KingKong method). I'm pretty sure no drive will resist firmwares creators whereas kernel>4552 will certainly resist a lots.
Logged
Pages: 1 ... 14 15 [16] 17