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.This Exploit Posted in 2019, Did you mentioned the developer who publish it 3 years ago??
At least change the classes names !!!!!!!!![]()
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.....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.
![]()
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.
Waiting for your FleetKey(aka S22 Snapdragon root) any update?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.....
can u share the steps after starting the shell exploit?
Me too, a huge thanks <3
Looks like you have already changed csc. Good.
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 . . .
/data/local/tmp
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
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 . . .
where di u download this from?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
View attachment 5843605
Edit:
All the other functions work fine however.
View attachment 5843607
View attachment 5843609
nc -lp 9999
am start -n com.samsung.SMT/.gui.DownloadList
You do know you can change the csc without this tool right?@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
That's why we've been removing posts.
- ... 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
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.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.
While this might not be considered development under our criteria, Rule 13 still applies as well: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;
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;
Yes, that's correct. I've update the original post.@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:
GitHub - flankerhqd/vendor-android-cves: Collections of my POCs for android vendor CVEs
Collections of my POCs for android vendor...github.com
That's why we've been removing posts.
- ... 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
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.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.
While this might not be considered development under our criteria, Rule 13 still applies as well: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;
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;