Droidspaces v6.0.0 has been released..!
https://github.com/ravindu644/Droidspaces-OSS/releases/tag/v6.0.0
https://github.com/ravindu644/Droidspaces-OSS/releases/tag/v6.0.0
π₯10β€2π©1
New feature: Ability to backup the container as a tarball :)
π₯20β€2π±1π©1
Can anyone try the recently discovered "Copy Fail" vulnerability on Droidspaces?
https://github.com/tgies/copy-fail-c/releases/tag/v0.2.0
Looks like I don't have a supported kernel.
What is expected is gaining root access inside the container or total container escape.
https://github.com/tgies/copy-fail-c/releases/tag/v0.2.0
Looks like I don't have a supported kernel.
What is expected is gaining root access inside the container or total container escape.
π©1
Droidspaces
Can anyone try the recently discovered "Copy Fail" vulnerability on Droidspaces? https://github.com/tgies/copy-fail-c/releases/tag/v0.2.0 Looks like I don't have a supported kernel. What is expected is gaining root access inside the container or total containerβ¦
It seems like Google saved all ya all asses by turning off the core Android kernel configuration necessary for this vulnerability:
But that doesnβt mean we are immune to this kind of attack since non-GKI kernels exist.
We still gotta block the necessary syscalls needed for this kind of attack using seccomp for the greater good.
CONFIG_CRYPTO_USER_API_AEAD=yBut that doesnβt mean we are immune to this kind of attack since non-GKI kernels exist.
We still gotta block the necessary syscalls needed for this kind of attack using seccomp for the greater good.
β€3π©1
Droidspaces
Can anyone try the recently discovered "Copy Fail" vulnerability on Droidspaces? https://github.com/tgies/copy-fail-c/releases/tag/v0.2.0 Looks like I don't have a supported kernel. What is expected is gaining root access inside the container or total containerβ¦
Well, you are vulnerable on Linux Desktop
What happened was a Local Privilege Escalation, not a container escape.
Therefore, this is a kernel issue rather than an issue with Droidspaces.
However, we will work on a fix from our side if possible β€οΈ
What happened was a Local Privilege Escalation, not a container escape.
Therefore, this is a kernel issue rather than an issue with Droidspaces.
However, we will work on a fix from our side if possible β€οΈ
π¨3π©1