This page was created when knowledge was low, everything on here is impossible, due to the 360's hypervisor. The only exploit there is and ever will be is the King Kong/JTAG (SMC)/or any other exploit for the 4532 kernel - slasherking823
Actually, upon further examination, this page was created by someone with no knowledge even when public knowledge existed.
Bad Ideas are as follows:
Please reply and comment each attack and tell us if such attacks are possible or not
Please do not erase wrong things but reply instead
- Old Xbox games
- Known bugs on the old games
- Maybe it works (small probability that it has not been fixed)
- It's been noted that few of the Original Xbox's games whose game saves were exploitable appear on the Xbox 360 backwards list. However it's also worth knowing that games in addition to 007AUF, MA, and SC1 contain similar flaws - but their exploitation was not felt neccessary.
- This probably won't work, since the Xbox 360 emulates the old Xbox (with a customized emulator for each game). Using a bug in an old game would just "break out" into the emulated old Xbox. Of course, if the emulator design is sufficiently sloppy, it might be possible to have a second step that then compromises the actual Xbox 360 security.
- Patched games
- Patching (French)
- (Early Versions?) King Kong will need a patch in order to be playable on some screens
- The patch needs a HDD
- Manipulated media files
- Images, Music Files, Video
- Windows Media Center, after authenticating with the server, uses a client compiled for the 360 to access all Media Center functionality. The software is very buggy. It would be a prime target for attack.
- Start by trying out some exploits that are already known and see
how Xbox 360 reacts to them
- There is potential to use a .tiff overflow(?) Certainly if
the hypervisor behaves as suggested, it will catch the
buffer overflow, but it might provide insight as to how it
- I emailed the team that did the .tiff overflow with the PSP (for anyone who knows about their work), and asked for info regarding how they went about .tiff exploit. They had some interesting things to say (I can email anyone their response if they want), and recommended this. I'm sure it's old business for a lot of people, but its over my head; I'm not able enough to get a lot of it. If someone wants to work in conjunction with me to try this exploit out, my email is GBW88@comcast.net.
- Maybe the recent WMF bug (escape function) will work too.
- WMF Files don't play on the 360.
- There is potential to use a .tiff overflow(?) Certainly if the hypervisor behaves as suggested, it will catch the buffer overflow, but it might provide insight as to how it works.
- Images, Music Files, Video
- Save game attack
- Will require another hack first to be able to hijack a game's save game signing
- Network compromise
- Fuzzing services/network connections
- File system drivers
- Manipulating entries like the partition table, etc Hard Drive Mod.htm]
- Decompression routines
- Cause a buffer overflow
- DMA attack
- Someone has developed an exploit for Firewire DMA FireWire - all your memory belongs to us
- Firewire can copy data between two Firewire HDDs without using the CPU at all (no irq gestion ...)
- Maybe retrieve some data that can't be retrieved
- USB and IDE that have DMA
- Maybe it doesn't work with non-Firewire devices
- Video: 
- Manipulated USB
Torx and Solder
- Boot suggests various CPU parameters including the hypervisor mode and boot vector are set by the I2C/SPI bus on start up. If the I2C/SPI bus is accessible and modifiable then security features could be disabled allowing another vector to succeed.
- Theories are floating around some forums as to the validity of
hacking DVD drive firmware to authenticate all discs as OK. Firmware
has some basic bitswapping and xor-ing which was defeated quickly,
maybe potential to change it?
- Good technical thread
xboxhacker.net. Unfortunately, it starts in the name of backups,
but it contains large amounts of insight as to how the DVD
system functions. Signing code would still be a problem, but
bypassing mediachecks could help at least.
- (Offtopic) If it is possible to modify the firmware, would it then not also be possible to read the 'hidden' security areas on (for example) audio-dvd?
- Good technical thread here at xboxhacker.net. Unfortunately, it starts in the name of backups, but it contains large amounts of insight as to how the DVD system functions. Signing code would still be a problem, but bypassing mediachecks could help at least.
- If some bus are accessible but at too much high speed (don't remember well the design of the 360, I should re-read the documentation and websites) maybe use of highspeed DAC or professionals osciloscope for electronic design or aviation (maybe some people have access to such devices) or home-made ones (using some DAC of some cards (video-cards,tv-cards))
- Easiest way to do DAQ is to use an NI DAQ system of allmost any kind (w/ fast enough DAC, something like FLASH-DAC) 
- Develop program for a snatching data from the bus. with high input impendances, megaohm range. If somebody is able to get those DAQ systems, I'm going to write a program for snatching data.
To save people revisiting old ground please list any attempts that have failed here
This is a stub or whatever you call this kind of page...
It's as a "brouillon(french)" This page has not been reviewed by skilled persons... (maybe they haven't got the time) this page could be reviewed by someone that is not a developer (precious time) but is a press expert and know what is possible and what isn't.
So put evrything on the main page and discuss it on the main page it's meant for this.
And if something clean and verified can be produced we will make another "stable" page that developers should read.
Xbox 360's OS has its root in the OS of the original Xbox (which is derivate from Windows 2000). I think that some bug and exploit in the Original Xbox (or even 2000) still works on the 360, we have to try every bug/fuzzing/hole knowed to find exploits.
File format fuzzing (there are some tools in Sourceforge), example: image format like WMF (recent exploit in Win 2000 and XP platform due to implementation of the fct escape() and not a BO!!!!!)
XMA is a very good way to find some holes, and Sounds aren't signed (Demo DVD) Someone has Doc about XMA ? maybe in XACT ?
By network UPnP (use XML), it's seems that the norm thinks about security like not permit to send XML break char, or limit ACL hack, but if there are an XML implementation (libXML) there are chance to find an exploit.
We all know Microsoft's security in their implementation of norms (like IP stack or other).
By DMA, using USB (security hole in Win 2000\&XP ohcpi) other way: IDE (sata), we can try to access to DMA with a PC connected to the Xbox...by SATA ;-) the idea is to use the PC like an IDE device for the Xbox 360. I'm reading the DMA-API and IDE doc for Linux (if you have Linux, interessting stuff is in /include/Documentation/DMA-API.txt & DMA-mapping.txt and in /include/Drivers/ide/ )
By threads, if we can use the GPU to access to RAM and access to the same area as the CPU we can do some buggy things (in fact thread is not necessary)
Metasploit, a huge DB for exloits and shellcodes https://metasploit.com/
Milw0rm, exploits milw0rm.com
Fuzzing file and network http://rtos.trinux.org/secwiki/FuzzingTools
What security problems are known about the XEX files. They can be burned to DVD/CD and used to install the backwards compatability emulator, so attacking them would be a good idea. Since the OS for the 360 is based on Windows, is the .xex file in any way related to .exe? .xex files renamed to end in .exe do not do anything in Windows. I would like further documentation on what happens when the emulation software is executed via CD/DVD. -- Monsuco 19:29, 9 Mar 2006 (CET)
The Xbox 360 CPU is based on the PowerPC architecture, not on Intel like PC CPUs. For that simple reason, an Xbox 360 executable will never run under a PC version of Windows. --Silence 10:59, 10 Mar 2006 (CET)
First guy is absolutely retarded >_> - Thilo
- The XNA libraries are .NET wrappers around various DirectX libraries (XACT, XInput, Direct3D, etc), and runs on the .NET Compact Framework. Both frameworks are fairly large and complex and it could be a possible candy store for exploits.