Skip to playerSkip to main content
  • 2 days ago
PS4 BD-JB has been updated to a remote jar loader for executing jar payloads sent over the network.
--------------------------------------------------------------------------------------------------------
Links:

BD-JB: https://github.com/Gezine/BD-JB-1250

NetCat GUI: https://www.sendspace.com/file/v765gd

imgburn: https://www.imgburn.com/index.php?act...
--------------------------------------------------------------------------------------------------------
Music
Outro: Paul Flint - Sock It To Them - • Paul Flint - Sock It To Them [NCS Release]
--------------------------------------------------------------------------------------------------------
Find my content on these other platforms:
Odysee: https://odysee.com/@MODDEDWARFARE
LBRY: https://lbry.tv/@MODDEDWARFARE
BitChute: https://www.bitchute.com/channel/cZkN...
Transcript
Transcript
00:00Hey, how's it going guys? Welcome back to another PS4 video. So we already have an update to the
00:04Blu-ray drive exploit that works up to 12.50. Now again, this is a user land only exploit at the
00:11moment. So yes, it works up to 12.50, but this is only a user land exploit. You cannot jailbreak up
00:17to 12.50. Of course, we need to basically chain this with an existing kernel exploit to be able
00:23to use it to jailbreak the console, which has not been done yet at the time of recording this
00:27particular video. And of course, the only kernel exploit we have right now is the lapse kernel
00:32exploit, which only works up to 12.02, which is why we'll only be able to jailbreak up to 12.02
00:37with this exploit, even though the exploit on its own works up to 12.50. Hopefully that clarifies
00:42that because I have seen some confusion about that recently. So anyway, that is the general idea. So
00:48the update here is that it's been transformed into a remote jar loader now, similar to the way the
00:54Blu-ray drive exploit on the PS5 works on its own. There is a remote jar loader. So the idea is that
01:00instead of having the Java files to execute on the ISO itself, the ISO just runs a listener,
01:07which then executes jar files that are sent to it over the network from another device like a phone
01:12or computer on the same network. And then that way, as new jar files are created, you'll be able to
01:17just send them to the console to try out different jar payloads as they come out. And as this exploit
01:23evolves over time, that is the general idea. So because this is a user land exploit on its own,
01:29and it's not being chained with a kernel exploit yet, there's not really going to be much that
01:32you can do with it on its own. Obviously, there's the hello world payload, which just prints a
01:37notification. We might eventually get an FTP server, which will be sandboxed FTP only. We might see
01:44those kind of jar payloads be made available, maybe some, maybe some Java based games or something
01:49like that that you could run. So to set this up, all you need to do is download the log client Python
01:54file here, and then also go to the releases section and grab the latest release. So download
01:59the jar file. So this is just a sample jar file to test it. Obviously, more jar payloads will be added
02:06as different payloads get developed that you can also then send to the console for this to execute.
02:12But for now, it's just the hello world dot jar file. And then we also have the ISO itself to burn
02:18to the disk. So download the ISO file, and then simply burn it to a disk using whatever software
02:23you normally use. I typically use image burn. So with image burn, you just go to write image file
02:28to disk, drag and drop the ISO into the program, and then select the option to burn the disk. And
02:35then that will get the ISO written to your Blu-ray. Once you have it on your Blu-ray, simply put in the
02:39disk into the console, and you should be more or less ready to go here. So at this point, you just want
02:45to make sure you have a network connection on your PS4 by heading into the system settings system,
02:50system information, and then check to make sure you have a valid IP address there on your network.
02:55So I have 192.168.137.85, which is fine. And then we can go ahead and load our Blu-ray disk on the
03:02PS4. And that should get the exploit up and running. Now another change with this particular version is it
03:10will also display the log on screen now on the PS4 itself. So you don't have to use the remote log
03:17to get the log on another device. You can just see the log here on the PS4 itself. So it says
03:22screen initialized, and then we have jar loader listening on port 9025. So we are all good to go
03:28there. So if we switch over back to our computer, you can just use most PS4 payload injectors to send
03:35the payload. Obviously you can use regular Netcat or Socat or something like that to send the payload.
03:41I'm just going to use Netcat GUI. So if I open up this program here, I'll take the hello world.jar
03:47file and drag it inside and then change the port number to 9025, which was the correct port number.
03:54And then of course, I also need to enter the correct IP address of the PS5 as well, which was
03:59ended in 137.85. And that's it. I can simply inject payload. And when I hit inject payload,
04:06we get the execution loading there on screen and we get our hello world payload executed.
04:11And that's it. And we get the log also showing the execution and everything that happened on the
04:16system as it ran that payload is now showing. And then once it is completed, we get execution
04:21completed and then waiting for the next jar on port 9025. So you can send another one. I can keep
04:26sending the same payload over and over again, as you can see, hello world, hello world. And it will
04:31keep printing it on screen. So you can send multiple jar files one after the other using this. Now,
04:38if you have Python installed on your computer, you can also get the remote log using the log client
04:43Python file here. Basically, we just right click and open in terminal to open up a PowerShell window
04:50in the same location as the file as the log client dot py. And then we'll run that by typing in
04:56Python. And then log underscore client dot py. And then the IP address of our PS4 137 dot 85.
05:08And then the port number, which I believe is 18194, it should be. And then we'll just press enter.
05:17And there we go. You can see we get the log now printed on my computer as well. So if I wanted to
05:23note down the log, I could do so. So this is definitely handy for testers, because as this
05:28exploit continues to get developed, especially as it is attempted to get ported with the lapse
05:34kernel exploits, there's going to be a lot of testing that needs to be done. And having the
05:38Blu-ray exploit in this form, where developers can create new jar files and test them by just
05:44sending them remotely to the console to execute one after the other, getting the remote log like this
05:50is just going to make things a lot easier. Now, this is almost exactly the same way as the PS5
05:55Blu-ray drive exploit is implemented with the remote jar loader. Although the jar payloads for the PS5
06:01version will not work on the PS4. We need, you know, specific versions that are created for the PS4
06:09in order to work. So don't try and use the PS5 ones on the PS4. But we will eventually get other
06:15payloads, I'm sure, like potentially an FTP server payload, similar to the FTP snapshot one on the
06:21PS5, which gives you sandboxed FTP, which gives you only access to the file system that is contained
06:28within the sandbox. So usually just the files for the currently running application. And that's pretty
06:33much it until it can be chained with, of course, the lapse kernel exploits when we'll be able to
06:38actually use it to fully jailbreak the console. So anyway, that's going to pretty much do it for me.
06:43Just a quick update there. We now have a remote jar loader version of the Blu-ray drive exploit for
06:47the PS4 working up to 12.50. So hope you guys enjoyed this one or found the information useful.
06:52If you did, please leave a like and subscribe. And once again, I'll hopefully see you guys in the next one.
07:13Bye.
Be the first to comment
Add your comment

Recommended