MobSF: CSRF checks not enforced after Django migration
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| MobSF | Mobile-Security-Framework-MobSF | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Mobsf | Mobile Security Framework |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-3p54-567p-2wpr | MobSF's CSRF checks not enforced after Django migration |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.264% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Mobsf
Mobsf mobile Security Framework |
|
| Vendors & Products |
Mobsf
Mobsf mobile Security Framework |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | MobSF is a mobile application security testing tool used. Prior to 4.5.1, mobsf/MobSF/settings.py places django.middleware.csrf.CsrfViewMiddleware only in the deprecated MIDDLEWARE_CLASSES setting and omits it from the active MIDDLEWARE tuple, allowing a remote attacker to make a logged-in victim submit cross-site POST requests to authenticated web endpoints including /delete_scan/, /upload/, /download_scan/, /change_password/, /create_user/, and /delete_user/. This can delete scans, upload or download applications, change passwords, or manage users with the victim account permissions. This issue is fixed in version 4.5.1. | |
| Title | MobSF: CSRF checks not enforced after Django migration | |
| Weaknesses | CWE-352 | |
| References |
|
|
| Metrics |
cvssV3_1
|