CVE-2024-29190: MobSF SSRF Vulnerability on assetlinks_check(act_name, well_knowns)

Published Mar 22, 2024
·
Updated

Summary While examining the "App Link assetlinks.json file could not be found" vulnerability detected by MobSF, we, as the Trendyol Application Security team, noticed that a GET request was sent to the "/.well-known/assetlinks.json" endpoint for all hosts written with "android:host". In the AndroidManifest.xml file.

Since MobSF does not perform any input validation when extracting the hostnames in "android:host", requests can also be sent to local hostnames. This may cause SSRF vulnerability.

Details Example <intent-filter structure in AndroidManifest.xml:

<intent-filter android:autoVerify="true"> <action android:name="android.intent.action.VIEW" /> <category android:name="android.intent.category.DEFAULT" /> <category android:name="android.intent.category.BROWSABLE" /> <data android:host="192.168.1.102/user/delete/1#" android:scheme="http" /> </intent-filter>

We defined it as android:host="192.168.1.102/user/delete/1#". Here, the "#" character at the end of the host prevents requests from being sent to the "/.well-known/assetlinks.json" endpoint and ensures that requests are sent to the endpoint before it.

<img width="617" alt="image" src="https://github.com/MobSF/Mobile-Security-Framework-MobSF/assets/150332295/c570cb00-e947-4ad7-af80-26d46c0ad3f7">

PoC https://drive.google.com/file/d/1nbKMd2sKosbJef5Mh4DxjcHcQ8Hw0BNR/view?usp=sharelink

Impact The attacker can cause the server to make a connection to internal-only services within the organization's infrastructure.

Other sources

Mobile Security Framework (MobSF) is a pen-testing, malware analysis and security assessment framework capable of performing static and dynamic analysis. In version 3.9.5 Beta and prior, MobSF does not perform any input validation when extracting the hostnames in android:host, so requests can also be sent to local hostnames. This can lead to server-side request forgery. An attacker can cause the server to make a connection to internal-only services within the organization's infrastructure. Commit 5a8eeee73c5f504a6c3abdf2a139a13804efdb77 has a hotfix for this issue.

MITRE

Affected Software

2 affected componentsFixes available
pip/mobsfscan<0.3.8
0.3.8
Opensecurity Mobile Security Framework<3.9.7

Event History

Mar 22, 2024
CVE Published
via MITRE·10:12 PM
Data Sourced
via MITRE·10:12 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·11:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·11:54 PM
Data Sourced
via GitHub·11:54 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2024-29190?

CVE-2024-29190 is considered a moderate severity vulnerability that could potentially expose sensitive information.

2

How do I mitigate CVE-2024-29190?

To mitigate CVE-2024-29190, ensure that your application is using MobSF version 0.3.8 or later.

3

What is the impact of CVE-2024-29190?

The impact of CVE-2024-29190 is that it may allow unauthorized access to the assetlinks.json file, leading to security risks.

4

Which versions of MobSF are affected by CVE-2024-29190?

CVE-2024-29190 affects all versions of MobSF prior to 0.3.8.

5

How can I check if my application is vulnerable to CVE-2024-29190?

You can check if your application is vulnerable to CVE-2024-29190 by performing a security scan using MobSF.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203