Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CVE-2022-40297 PoC — Ubuntu Touch 安全漏洞

Source
Associated Vulnerability
Title:Ubuntu Touch 安全漏洞 (CVE-2022-40297)
Description:Ubuntu Touch是UBports Foundation基金会的一个移动设备操作系统。专为触屏行动设备所设计。 UBports Foundation Ubuntu Touch 16.04版本存在安全漏洞,该漏洞源于密码只有四位数字,远低于用户帐户密码的典型长度/复杂性。
Description
CVE-2022-40297 - Proof of Concept: Privilege escalation in Ubuntu Touch 16.04 - by PIN Bruteforce
Readme
![screen](img/ubuntutouch.gif)

[UPDATE 09.09.2022] I got new CVE for this vulnerability: [CVE-2022-40297](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-40297).

## Proof of Concept: Privilege escalation in Ubuntu Touch 16.04 - by Passcode Bruteforce 

Ubuntu Touch allows you to "protect" devices with a 4-digit passcode. Such a code was set in a demonstration device. The problem is that the same 4-digit passcode then 
becomes a password that we can use with the sudo command and gain root privileges.

This means that a malicious application can do us double harm:
1. Easily escalate privileges and take control of the device.
2. It can pass the screen unlock passcode to a third party.

## How does my Proof of Concept work?

1. We run poc.py as a regular user.
2. App is doing bruteforce attack on password. No rate limit in system!
3. Passcode to unlock the screen = password for sudo su to obtain root.
4. After 1-2 minutes we have passcode on the screen, which we also save to the file /root/passcode as evidence of system compromise.

## Follow me

Follow me on [Twitter @FilipKarc](https://twitter.com/FilipKarc) and on LinkedIn: [LinkedIn](https://www.linkedin.com/in/filip-karczewski/).



![screen](img/screen2.png)


![screen](img/screen3.png)




  
File Snapshot

[4.0K] /data/pocs/d86dbf3ff2cb76d03ec35d0903b79fb1f373be8d ├── [ 166] CONTACT.txt ├── [4.0K] img │   ├── [1.1M] screen2.png │   ├── [874K] screen3.png │   └── [ 13M] ubuntutouch.gif ├── [ 11K] LICENSE.txt ├── [ 859] poc.py └── [1.2K] README.md 1 directory, 7 files
Shenlong Bot has cached this for you
Remarks
    1. It is advised to access via the original source first.
    2. If the original source is unavailable, please email f.jinxu#gmail.com for a local snapshot (replace # with @).
    3. Shenlong has snapshotted the POC code for you. To support long-term maintenance, please consider donating. Thank you for your support.