Consider CVE-2023-21385 which was discovered in AOSP. In this security bulletin , they mentioned that this issue was fixed. Is there any chance to know what kind of fix was given to this CVE (code changes done) that I can take a look at as it is an open-source project?

I am working on an Android Java application that performs a vulnerability scan of the network where the mobile device is. Since I cannot install any type of vulnerability scan tool on Android I would like to send the vulnerability scan packets from a back-end server (running open-vas) to my android device and then make the android device forward them to the destination hosts inside his network. The easiest way to do that would be to create a VPN Server on the android device, but I don't think it's possible with the VpnService APIs. From what I have found it looks like someone managed to forward traffic with VPN Service: Android VpnService - How to forward intercepted internet traffic . Another idea was to create a sort of packet wrapping: I can wrap the original packet coming from the back-end server inside a standard TCP packet, send it to the android device, unwrap it and forward it to the host inside the device's network. Although I don't know if this would really work in my case for 2 main reasons: 1. I will probably receive RAW packets from the server (since vulnerability scanners forges specific RAW packets for vulnerability testing) and Java does not have any support for manipulating packets 2. Even if I am able to unwrap the packet I will still have a RAW packet to send and from what I have seen Java does not have any support for RAW sockets for security reasons. So do you guys have an idea if there is a way to create a VPN Server on Android to do this remote vulnerability scan? Thanks! PS Maybe rooting the device will give some more alternatives but I am reserving this as last chance.

I have two smartphones running Android 10 and 8, The ADB is enabled for many proposes. Generally some vendors have been shipping products with Android Debug Bridge enabled. But it seems that enabling ADB have many security risks according to DoublePpulsar blog: Root Bridge — how thousands of internet connected Android devices now have no security, and are being exploited by criminals. >This is highly problematic as it allows anybody — without any password — to remotely access these devices as ‘root’* — the administrator mode — and then silently install software and execute malicious functions. Does the latest Android releases are secure against the ADB vulnerability?

A vulnerability, CVE-2020-0022 , was recently announced in some versions of Android. My phone, a Sony Xperia XA2, does not *yet* have an update available. What should I do in the meantime? The report suggests "Only enable Bluetooth if strictly necessary". Is it sufficient to disable by tapping the button on the "swipe-down" panel or does it require a deeper configuration change? The report also suggests "Keep your device non-discoverable". Is it perhaps sufficient to leave discoverability switched off until an update is available? If leaving discoverability switched off was not sufficient mitigation, why would the report even mention it?

>**Background Info:** CVE-2019-2234 is a serious vulnerability or (maybe an APT) which allow other apps to record videos, take pictures, and extract EXIF data without having permissions. > >**Edit:** This question is other devices rather than Pixel & Samsung I've tested this PoC (changed package name to my camera's package name) to check if is this possible on my (non Pixel) device, but all I have is the camera activity has been launched without starting recording or taking pictures. **Launch Camera:** adb shell am start-activity -n com.android.camera/com.android.camera.CameraActivity --ez extra_turn_screen_on true -a android.media.action.CAMERA --ez android.intent.extra.USE_FRONTAL_CAMERA true **Launch Video:** adb shell am start-activity -n com.android.camera/com.android.camera.CameraActivity --ez extra_turn_screen_on true -a android.media.action.VIDEO_CAMERA --ez android.intent.extra.USE_FRONTAL_CAMERA true **Question** **Part 1:** If this device is vulnerable are there other extras to add to make the PoC work and proof that it's vulnerable? or just it's not? **Part 2:** If the device is vulnerable, what would be the best mitigation solution for this?