0:00
what's going on youtube gsm right here
0:02
so in today's video we have some great
0:03
news for those of you waiting for
0:05
jailbreak on ios 15.0 15.0.1 15.0.2 and
0:10
15.1 a brand new exploit seems to have
0:12
been achieved this video is brought to
0:14
you by any trans a software that allows
0:16
you to drag and drop files directly from
0:17
your computer to your device manage your
0:19
photos music videos and applications and
0:21
even switch from a device to another if
0:23
you get a new device check it out in the
0:25
link below so just a couple of hours ago
0:29
wbb posted the hash for basically a text
0:32
file called ios 15 code execution zero
0:35
day so apparently this is a zero data
0:37
loss code execution on ios 15 but they
0:39
do not have any plans to release it for
0:41
the moment the reason for that is that
0:43
it seems to be zero days so if it's zero
0:46
day it means that not even apple knows
0:48
what's going on for the moment basically
0:50
they are the only developer presumably
0:52
that know about the vulnerability and
0:54
that have created an exploit for it now
0:56
this is not the first of this kind brady
0:58
posted at the beginning of the month
1:00
this photo in here which apparently
1:01
seems to be another kernel exploit for
1:03
ios 15.1 which also got the kernel slide
1:06
and read and write privileges because as
1:08
you can see they call wk64 or right
1:11
kernel 64 and rk64 or read kernel 64 and
1:15
they do work and that is on the iphone
1:17
13.4 now i'm not sure if this is the
1:19
same bug if they sound basically the
1:22
same vulnerability and they have their
1:23
own zero day but found it independently
1:26
or if it's actually a completely
1:27
different bug but both of them aren't
1:29
currently released because of course
1:31
they are zero day which means that
1:32
they're not part of any security release
1:34
they are not patched yet which means
1:36
they work on the latest version because
1:38
if you check out here on my website when
1:39
i device central if you select the
1:41
device you're going to see that ios 15.1
1:43
is currently the latest version so 15.1
1:46
currently signed now if this works on
1:48
15.1 there is a slight chance it would
1:50
work on 15.0 15.0.1 and 15.0.2 as well
1:54
and probably even older if you think
1:56
about it it could work on 14.8 14.7 as
2:00
well but they tested on ios 15 because
2:02
14 is basically dead and buried at this
2:04
point it's been unsigned for a long time
2:06
and ios 15 has had already like four
2:09
different iterations of stable releases
2:12
and a lot of bait tests so ios 14 point
2:14
x is no longer the target of security
2:16
researchers but as time passes they will
2:19
release what they have for ios 14.6 14.7
2:22
and so on now will this be usable for
2:25
uncover or for taurine well it depends
2:27
on what this contains code execution is
2:30
great and it can be used for jailbreak
2:31
purposes but it depends on what it can
2:33
achieve and how constrained it is we
2:36
don't know much about this but we do
2:37
know that this one here by brady app has
2:40
kernel read and write privileges so this
2:42
one is definitely usable for a jailbreak
2:44
because of the read and write
2:45
permissions you can read and write to
2:47
the kernel memory thus applying patches
2:49
which are required for jailbreaking like
2:51
for example get root or escape sandbox
2:53
and patch and feed and stuff like that
2:55
so those require it to have primitives
2:57
that can read and write to the kernel
2:59
memory now we don't know if this one
3:00
here does the same thing it could it
3:02
could be the same bug for all we know
3:04
probably not but it could be so until
3:06
any of these get released we don't know
3:08
much at the moment however it's nice
3:10
that they are indeed achieved because
3:13
ios 15 does change a lot as i said in my
3:15
previous videos there are some changes
3:17
that would break chill breaking that
3:19
need to be addressed by either uncover
3:21
or taurine when they're going to update
3:22
their tools so it's good to see that
3:24
it's still vulnerable it's still rather
3:26
easy to find vulnerabilities in ios 15
3:28
but those are zero day for the moment so
3:30
we wouldn't expect them right now so
3:32
what's the best course of action for now
3:34
if you're waiting for uncover or touring
3:35
to be updated and you're running ios 15
3:38
14.8 14.7 14.6 and so on well i would
3:41
definitely not advise you to update the
3:44
15. it's a bad idea do not update the
3:46
15.1 no matter how many vulnerabilities
3:48
are demoed stay as low as possible but
3:51
save your blobs you can use the
3:52
airsquared blob saver here i made a
3:54
tutorial a couple of days ago you can
3:56
find it here on releases and it's
3:58
available for both windows mac os linux
4:00
and stuff and you will be able to save
4:01
your blobs even on the a12 and newer
4:03
devices save your blobs for the ios 15.1
4:06
so that you can jump to it when the
4:08
opportunity arises and of course when a
4:10
jailbreak is available where an exploit
4:12
gets released but for now stay as low as
4:14
possible if you're running 14 point x
4:17
remember that not even check ring can
4:18
jailbreak properly the ios 15 at the
4:20
moment it would fail so definitely stay
4:23
on ios 14 for now thank you for watching
4:25
imgs now until the next time subscribe
4:27
to stay updated peace out
