***LOCKED UNTIL FURTHER NOTICE*** System Shell Exploit - ALL Samsung Mobile Devices NO BL UNLOCK REQUIRED.

Status
Not open for further replies.
Search This thread

franzzzV6

New member
Apr 16, 2013
2
0
samsungTTSVULN2.apk: 1 file pushed, 0 skipped. 62.5 MB/s (15955101 bytes in 0.243s)
Performing Streamed InstallSuccess
Failure [-3005: INSTALL_FAILED_ADP_VERSION_LOCKED]
ROLLBACK FAILED
 

adfree

Senior Member
Jun 14, 2008
10,320
6,034
Samsung Galaxy Watch 4
Samsung Galaxy S22
System Shell Exploit still working on Galaxy Watch 4 with February Firmware Update GWB1...

Tested with SM-R860:

Looks Security Patch is same like in older GWA3... January...


I have NO idea nor read real feedback if Firmware Update kills System Shell Exploit...

Something like BEFORE it runs... now after Firmware Update XYZ not.

Oh forgotten. GW4 is still Android 11 crap...

Best Regards
 
  • Like
Reactions: Jacob1004
Any idea why the easy mode EXE would be complaining it can't find AdbWinApi.dll? I've got the platform-tools files copied into the same folder as the EXE, but it seems like the EXE is not looking in its own directory for the DLL. Is there a specific place it is trying to look? (Windows 11 Insider, btw.)
 

adfree

Senior Member
Jun 14, 2008
10,320
6,034
Samsung Galaxy Watch 4
Samsung Galaxy S22

@dwkindig


If you follow @oakieville post here and/or on Telegram Group...

Because he creates these wonderfull colored EXEs...

A
Last ehm latest EXE is all in 1 package...

ALL files inside EXE...
Means both APKs AND ADB Files...

B
He packed and crypted and packed and crypted... so Antivirus Programs detect """something""" inside this magic EXE...

B.1
"he" wrote IMHO he unpack temporary ADB Files and/or all files into """temp""" folder...


So it could be your Antivirus let you execute the "EXE" but kills/block/stop or whatever doing with the temporary extracted files...

I NEVER found what he meant with temp...


I have tested successfully under Win 7 and Win 10 and Win 11...

With Avira Antivir... by disable adb folder for Virus Scanning...

I have NEVER seen this missing DLL Bug ehm Feature...


I have only successfully tested with Avira...

McAfee for instance no idea... I have uninstalled this ... and replaced with Avira...

I posted few times my summary...

Maybe IMHO it makes sense to give more details... maybe you can "replace" EXE with other solution posted here...

For me only the EXE work... but I am playing only with Watch.


Best Regards

Edit 1.

Here how it looks on my Windows 11 Notebook...

Few posts earlier Win 10... and Win 7...

So it is no matter of Windows Version... It depends on your Antivirus "Settings"...
 
Last edited:

darenfy

New member
Feb 10, 2023
1
0
I've successfully run and gotten a system shell on the device, thanks a lot.

What makes me very curious is how you got your SamsungTTSVULN2.apk.

I also try to get one available. There are no historical versions of apps in the Samsung App Store; installations of historical versions of apps from third-party app markets return INSTALL_FAILED_REJECTED_BY_BUILDTYPE.
I even manually extract the old version SamsungTTS.apk on ancient Samsung phones and install on new Samsung phones, but it still returns INSTALL_FAILED_REJECTED_BY_BUILDTYPE, which confuses me
 

imatary

New member
Sep 17, 2010
2
1
This Exploit Posted in 2019, Did you mentioned the developer who publish it 3 years ago??

At least change the classes names !!!!!!!! :)
 
  • Like
Reactions: gaelikitten

gaelikitten

New member
Jul 24, 2022
4
6
Samsung Galaxy S22 Ultra
This Exploit Posted in 2019, Did you mentioned the developer who publish it 3 years ago??

At least change the classes names !!!!!!!! :)
Someone pointed this out in the telegram channel for this and they just deleted it. Would be nice if credit was given where it was due.

You can see this very clearly if you take a look at the binary libmstring.so that is distributed with the POC, it still has the quirky comments in it from flanker017's write-up of this exploit. It isn't much to ask for a simple thanks to him as well, as clearly without this look at this CVE we wouldn't be talking about this issue.
SpQ7Qhv.png

It's all still there. And yet, not a mention of his work. I know plagiarism isn't really something people care about online, but if I were a security researcher I would want to make sure that those who worked on this are given their just attribution.
There are shoutouts on the first post in this thread, and not a single person on that list should be any higher than flanker017. It would be one thing if you had based your exploit on his work, but considering it launched as a repackaging of his work, he should be given credit.
It's awesome what people are managing to figure out with this exploit. It's great. But without the foundation laid out by flanker017 we wouldn't be posting in this thread today.
 
Last edited:
Someone pointed this out in the telegram channel for this and they just deleted it. Would be nice if credit was given where it was due.

You can see this very clearly if you take a look at the binary libmstring.so that is distributed with the POC, it still has the quirky comments in it from flanker017's write-up of this exploit. It isn't much to ask for a simple thanks to him as well, as clearly without this look at this CVE we wouldn't be talking about this issue.
SpQ7Qhv.png

It's all still there. And yet, not a mention of his work. I know plagiarism isn't really something people care about online, but if I were a security researcher I would want to make sure that those who worked on this are given their just attribution.
There are shoutouts on the first post in this thread, and not a single person on that list should be any higher than flanker017. It would be one thing if you had based your exploit on his work, but considering it launched as a repackaging of his work, he should be given credit.
It's awesome what people are managing to figure out with this exploit. It's great. But without the foundation laid out by flanker017 we wouldn't be posting in this thread today.
Be rest assured that credit will be formally made. As many of us..have busy lives and things have got a bit busier. Things get missed and we're only human. But I'll make sure the right information is posted and also make sure...to give credit where it's needed. I'll pass the world on to k0mraid3. Thanks.....
 

adeelraj230

New member
Oct 13, 2022
2
1
Be rest assured that credit will be formally made. As many of us..have busy lives and things have got a bit busier. Things get missed and we're only human. But I'll make sure the right information is posted and also make sure...to give credit where it's needed. I'll pass the world on to k0mraid3. Thanks.....
Waiting for your FleetKey(aka S22 Snapdragon root) any update?
 

adfree

Senior Member
Jun 14, 2008
10,320
6,034
Samsung Galaxy Watch 4
Samsung Galaxy S22
New day, new attempt to "replace" 1 day in 2023 the EXE for my Galaxy Watch 4...


The "new" idea in my tiny brain is to split Batch Files instead wholeIn1...

First attempt... then I will check "second" Button in beautiful colored EXE...

Code:
D:\Android\adbLEAK>A_install_AND_push_2APKs_v1.bat

D:\Android\adbLEAK>adb push .\apk4exploit\samsungTTSVULN2.apk /data/local/tmp
.\apk4exploit\samsungTTSVULN2.apk: 1 file pushed, 0 skipped. 3.3 MB/s (15955101 bytes in 4.605s)

D:\Android\adbLEAK>adb install .\apk4exploit\komraids_POC_V1.5.apk
Performing Streamed Install
Success

D:\Android\adbLEAK>pause
Drücken Sie eine beliebige Taste . . .


Later if something successfull I can upload...

For now only for my tiny brain and Windows...

Interesting 1...
Code:
/data/local/tmp

This tmp folder is not self cleaning... so you can safe for looong time...

Because over this s hitty WiFi in Galaxy Watch 4... to prevent to transfer "huge" files tooo often...

Edit 1.

Could be the Rollback Command not included in second EXE Button...

Edit 2.
Memo to me... EXE 2Button with my Batch A not success...

Will create second Batch with Rollback and chmod... maybe mandatory... who knows...
Code:
freshbs:/ $ cd /data/local/tmp
freshbs:/data/local/tmp $ ls -a1l
total 15606
drwxrwx--x 2 shell shell     3452 2023-02-17 06:00 .
drwxr-x--x 4 root  root      3452 2023-01-29 05:09 ..
-rw-rw-rw- 1 shell shell 15955101 2023-01-18 19:11 samsungTTSVULN2.apk
freshbs:/data/local/tmp $ chmod 777 samsungTTSVULN2.apk
freshbs:/data/local/tmp $ ls -a1l
total 15606
drwxrwx--x 2 shell shell     3452 2023-02-17 06:00 .
drwxr-x--x 4 root  root      3452 2023-01-29 05:09 ..
-rwxrwxrwx 1 shell shell 15955101 2023-01-18 19:11 samsungTTSVULN2.apk

Edit 3.

Batch 2...

Code:
D:\Android\adbLEAK>adb shell chmod 777 /data/local/tmp/samsungTTSVULN2.apk

D:\Android\adbLEAK>adb shell pm install -r -d -f -g --full --install-reason 3 --enable-rollback /data/local/tmp/samsungTTSVULN2.apk
Success

D:\Android\adbLEAK>pause
Drücken Sie eine beliebige Taste . . .

Edit 4.

chmod seems not mandatory...

Still no success...
 
Last edited:

omaralwardian

Member
Apr 9, 2020
37
11
New Brunswick
After installing 2.0.3 and providing permission to the escalation app and running the app, everything runs fine except for when I go to the custom command option and type in the provisions to set the camera2API which require SAF.

This is what it says.

@adfree @K0mraid3
Screenshot_20230221_192919_Samsung Toolkit.jpg



Edit:

All the other functions work fine however.

Screenshot_20230221_193533_Samsung Toolkit.jpg

Screenshot_20230221_193537_Service mode RIL.jpg
 
  • Like
Reactions: hinderless

subevilx

Member
Dec 30, 2022
34
8

kiranambati

Member
Apr 30, 2015
7
5
@K0mraid3 @adfree

Can you please help me with the issue I am facing?
Device : Galaxy watch 5 pro
I have tried all the steps given in manual way. but not able to get to the shell. it is stuck at

nc -lp 9999

Here is the screenshot
1677101956601.png


As mentioned I ran am start -n com.samsung.SMT/.gui.DownloadList in another shell

am start -n com.samsung.SMT/.gui.DownloadList
1677102012521.png


Which opened language installation screen on my watch

1677102165279.png


Can you please guide me where is the mistake?
I want to change CSC code of the watch.
please let me know if you need anymore details

TIA
 
  • Like
Reactions: Kgstate and adfree

Sands207

Senior Member
Oct 13, 2014
1,312
682
Maine
Samsung Galaxy A32 5G
@K0mraid3 @adfree

Can you please help me with the issue I am facing?
Device : Galaxy watch 5 pro
I have tried all the steps given in manual way. but not able to get to the shell. it is stuck at

nc -lp 9999

Here is the screenshot
View attachment 5844451

As mentioned I ran am start -n com.samsung.SMT/.gui.DownloadList in another shell

am start -n com.samsung.SMT/.gui.DownloadList
View attachment 5844461

Which opened language installation screen on my watch

View attachment 5844463

Can you please guide me where is the mistake?
I want to change CSC code of the watch.
please let me know if you need anymore details

TIA
You do know you can change the csc without this tool right?
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    ***MODERATOR ANNOUNCEMENT: THREAD CLOSED***

    @K0mraid3 you are hereby required to provide proper credit in your OP as follows:
    • Link the assigned CVE for this exploit as it mentions the author's blog and GitHub, OR
    • Link the original research repo as provided by @flanker017
    Further, while you may provide a means for donation, this project must remain free without condition of payment.

    Lastly, as you've been previously warned, you may not promote your Telegram channel on XDA. You may have ONE link to your TG channel in the OP.

    You must meet these conditions to continue to use XDA to share this project.

    As you have ignored my PM and previous warning, this thread is now CLOSED to further discussion. All download links relating to this project have been removed.

    This thread will remain closed until such time that @K0mraid3 is willing to comply with the above conditions.
    6
    Last warning: If you can't keep your bickering to PM and can't treat each other with respect, this thread will be locked. We don't want to do that, as with keeping in the "hacker" spirit of XDA, threads like this are the bread and butter of what we do.
    • ... and Please! keep all your personal bickering via PMs, do not pollute the forum with your personal indifferences.
      If you have a problem with a specific member please contact the Moderators for help, that's what we're here for, but we are not babysitters, we are here to gather, organize and provide useful information for our over priced phones
    That's why we've been removing posts.
    I've been quietly watching this for a while and I agree. I also find it unsettling that admins have removed the post discussing this issue.
    It's not that the questions shouldn't be asked, it's that they shouldn't be asked here. I'm going to start a PM thread involving a few of you so that we can get this straightened out.

    Now, more to the point: If you've used anyone else's source as a basis for your work, you MUST give them credit:
    12.1. Give credits where due - Credits and acknowledgements for using and releasing work which is based on someone else's work are an absolute must. Works reported to have no credits will be taken down until proper acknowledgements are added by the member in question;
    While this might not be considered development under our criteria, Rule 13 still applies as well:
    12.3. Re-releasing other's works as your own is forbidden. The code that you release into the wild must have something beyond minor aesthetic changes that makes it better than the last. As this can be subjective, kang reports will be reviewed on a case by case basis. If you feel that your code has been kanged, please contact the Developer Relations Team (DRT) if you cannot solve the issue amicably via PM. Please understand that you will be asked to provide evidence to substantiate your claim;

    So. Knock it off with the squabbling. Keep this thread on topic. If you have issues with sources or credits or whatever, bring it up to us. If your comment doesn't have directly to do with facilitating this exploit or reporting your progress in your own efforts, keep it out of this thread.
    6
    Hi:

    I'm the original author of the SMT research (https://github.com/flankerhqd/vendor-android-cves/tree/master/SMT-CVE-2019-16253) and I have been notified about this thread. My original purpose to share my research is to help the community to better utilize and protect their devices, and to help the vendors to improve device security, and to help other researchers for technical insights. I'm always glad to see this research is given a new life, and helped someone else, and further development are welcome - but it should be legal, non-profit, with proper attribution, and in good faith. Sorry to hear about that the original research has not been properly given credit.

    To prove it's indeed me - same announcement as above can be found on the Github repo's README file.

    Thanks!
    4
    Moderator Announcement

    This is NOT a development thread and therefore I've sanitised it from all links to Telegram! Regarding social media links please observe that as an exemption from the last bullet of rule no. 5 of the XDA Forum Rules, we grant only developers the privilege to share references to their social media in their own development threads and if thorough support is provided in the thread. Additional information is also available here:
    Please refrain for sharing of social media references unless within your own development threads! @wr3cckl3ss1 I've deleted a few of your posts and I'd appreciate if you comply with my guidance in future. Thanks to everybody for your future cooperation.

    Regards
    Oswald Boelcke
    Senior Moderator

    CC: @V0latyle
    3
    @flanker017

    Can you please add your Github repo... you mentioned?

    So it is easier for me to look at your work... instead Google or other search.

    Thanx in advance.

    Best Regards

    Edit 1.

    If I use this Link:

    And look for Github... then I can find this:
    Yes, that's correct. I've update the original post.
  • 37
    ***MODERATOR ANNOUNCEMENT: THREAD CLOSED***

    @K0mraid3 you are hereby required to provide proper credit in your OP as follows:
    • Link the assigned CVE for this exploit as it mentions the author's blog and GitHub, OR
    • Link the original research repo as provided by @flanker017
    Further, while you may provide a means for donation, this project must remain free without condition of payment.

    Lastly, as you've been previously warned, you may not promote your Telegram channel on XDA. You may have ONE link to your TG channel in the OP.

    You must meet these conditions to continue to use XDA to share this project.

    As you have ignored my PM and
    previous warning, this thread is now CLOSED to further discussion. All download links relating to this project have been removed. This thread will remain closed until such time that @K0mraid3 is willing to comply with the above conditions.
    6
    Last warning: If you can't keep your bickering to PM and can't treat each other with respect, this thread will be locked. We don't want to do that, as with keeping in the "hacker" spirit of XDA, threads like this are the bread and butter of what we do.
    • ... and Please! keep all your personal bickering via PMs, do not pollute the forum with your personal indifferences.
      If you have a problem with a specific member please contact the Moderators for help, that's what we're here for, but we are not babysitters, we are here to gather, organize and provide useful information for our over priced phones
    That's why we've been removing posts.
    I've been quietly watching this for a while and I agree. I also find it unsettling that admins have removed the post discussing this issue.
    It's not that the questions shouldn't be asked, it's that they shouldn't be asked here. I'm going to start a PM thread involving a few of you so that we can get this straightened out.

    Now, more to the point: If you've used anyone else's source as a basis for your work, you MUST give them credit:
    12.1. Give credits where due - Credits and acknowledgements for using and releasing work which is based on someone else's work are an absolute must. Works reported to have no credits will be taken down until proper acknowledgements are added by the member in question;
    While this might not be considered development under our criteria, Rule 13 still applies as well:
    12.3. Re-releasing other's works as your own is forbidden. The code that you release into the wild must have something beyond minor aesthetic changes that makes it better than the last. As this can be subjective, kang reports will be reviewed on a case by case basis. If you feel that your code has been kanged, please contact the Developer Relations Team (DRT) if you cannot solve the issue amicably via PM. Please understand that you will be asked to provide evidence to substantiate your claim;

    So. Knock it off with the squabbling. Keep this thread on topic. If you have issues with sources or credits or whatever, bring it up to us. If your comment doesn't have directly to do with facilitating this exploit or reporting your progress in your own efforts, keep it out of this thread.
    6
    ***MODERATOR ANNOUNCEMENT: THREAD CLOSED***

    @K0mraid3 you are hereby required to provide proper credit in your OP as follows:
    • Link the assigned CVE for this exploit as it mentions the author's blog and GitHub, OR
    • Link the original research repo as provided by @flanker017
    Further, while you may provide a means for donation, this project must remain free without condition of payment.

    Lastly, as you've been previously warned, you may not promote your Telegram channel on XDA. You may have ONE link to your TG channel in the OP.

    You must meet these conditions to continue to use XDA to share this project.

    As you have ignored my PM and previous warning, this thread is now CLOSED to further discussion. All download links relating to this project have been removed.

    This thread will remain closed until such time that @K0mraid3 is willing to comply with the above conditions.
    6
    ***Moderator Announcement***

    Flaming and disrespect will absolutely not be tolerated. Repeated violations may result in account bans. Compliance with all XDA Forum Rules and Policies is MANDATORY for all members. While you're free to discuss the technical details and merits of this exploit, as well as the wisdom in deferring updates, you WILL treat each other with respect and dignity, and those who fail to do so will no longer be permitted to participate on XDA.

    In addition, keep your posts ON TOPIC.

    If you feel someone's posts violate the Forum Rules, use the Report button and let the moderator staff handle it before it becomes an issue.

    Don't make us get involved again.
    6
    Hi:

    I'm the original author of the SMT research (https://github.com/flankerhqd/vendor-android-cves/tree/master/SMT-CVE-2019-16253) and I have been notified about this thread. My original purpose to share my research is to help the community to better utilize and protect their devices, and to help the vendors to improve device security, and to help other researchers for technical insights. I'm always glad to see this research is given a new life, and helped someone else, and further development are welcome - but it should be legal, non-profit, with proper attribution, and in good faith. Sorry to hear about that the original research has not been properly given credit.

    To prove it's indeed me - same announcement as above can be found on the Github repo's README file.

    Thanks!