Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Dismantling Smart App Control (And SmartScreen) - 4 new initial access techniques with no security warnings or popups - including LNK mark-of-the-web bypass with over 5 years of ITW use Article: POC: #rephijack #lnkstomping

21,052 Aufrufe • vor 2 Jahren •via X (Twitter)

3 Kommentare

Profilbild von HotCakeX ✡︎ סגול
HotCakeX ✡︎ סגולvor 2 Jahren

Few notes for readers 1) SAC is for home users, App control for Business is the enterprise ver 2) WDAC cannot be bypassed like this. 3) Using legit certificate to sign malware doesn't end up good for the person acquired the cert. 4) Windows has a lot more than 2 security layers

Profilbild von Squiblydoo
Squiblydoovor 2 Jahren

Thanks for calling out code signing certs. :) Would you mind uploading a compiled copy of rep-check? It just makes it a little more accessible.

Profilbild von Joe Desimone
Joe Desimonevor 2 Jahren

done,

Ähnliche Videos

The latest loophole that third-party file manager apps were using to get access to files and folders under /Android/data and /Android/obb has been patched. As part of Android 11's Scoped Storage restrictions, apps that use the Storage Access Framework (SAF) to launch the documents picker are not supposed to be able to get access to files and folders under the /Android/data or /Android/obb directories. However, third-party file managers figured out that if they set the initial directory when launching the documents picker to either /Android/data or /Android/obb, the documents picker lets the user grant the app full access to directories. This loophole was patched in Android 13, but then another loophole was discovered that got around this. Since Android 13 only blocked apps from setting /Android/data or /Android/obb as the initial directory when launching the documents picker, it was quickly discovered that you could set the initial directory to one of the subdirectories under /Android/data or /Android/obb, thus the user could grant access to individual subdirectories one-by-one. However, this latest loophole was patched with a recent Google Play System Update. The latest version of the DocumentsUI app, the Project Mainline module that comprises the documents picker, now restricts the initial location for the ACTION_OPEN_DOCUMENT/_TREE intent so that apps cannot request the initial location to be one of /Android/data, /Android/sandbox, /Android/obb, or one of their subdirectories. If the DocumentsUI app (AKA 'Files' app) on your device is on version 14-10492947 (version code 340916000), then this loophole is patched.

Mishaal Rahman

17,039 Aufrufe • vor 2 Jahren