Vulnerability Details : CVE-2023-42261
Potential exploit
Mobile Security Framework (MobSF) <=v3.7.8 Beta is vulnerable to Insecure Permissions. NOTE: the vendor's position is that authentication is intentionally not implemented because the product is not intended for an untrusted network environment. Use cases requiring authentication could, for example, use a reverse proxy server.
Products affected by CVE-2023-42261
- cpe:2.3:a:opensecurity:mobile_security_framework:*:*:*:*:*:*:*:*
- cpe:2.3:a:opensecurity:mobile_security_framework:3.7.8:beta:*:*:*:*:*:*
Exploit prediction scoring system (EPSS) score for CVE-2023-42261
0.22%
Probability of exploitation activity in the next 30 days
EPSS Score History
~ 42 %
Percentile, the proportion of vulnerabilities that are scored at or less
CVSS scores for CVE-2023-42261
Base Score | Base Severity | CVSS Vector | Exploitability Score | Impact Score | Score Source | First Seen |
---|---|---|---|---|---|---|
7.5
|
HIGH | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
3.9
|
3.6
|
NIST |
CWE ids for CVE-2023-42261
-
During installation, installed file permissions are set to allow anyone to modify those files.Assigned by: nvd@nist.gov (Primary)
References for CVE-2023-42261
-
https://github.com/woshinibaba222/hack16/blob/main/Unauthorized%20Access%20to%20MobSF.md
hack16/Unauthorized Access to MobSF.md at main · woshinibaba222/hack16 · GitHubExploit
-
https://github.com/MobSF/Mobile-Security-Framework-MobSF/blob/abb47659a19ac772765934f184c65fe16cb3bee7/docker-compose.yml#L30-L31
Mobile-Security-Framework-MobSF/docker-compose.yml at abb47659a19ac772765934f184c65fe16cb3bee7 · MobSF/Mobile-Security-Framework-MobSF · GitHubPatch
-
https://github.com/MobSF/Mobile-Security-Framework-MobSF/issues/748
Do you have authentication for MobSF? · Issue #748 · MobSF/Mobile-Security-Framework-MobSF · GitHubIssue Tracking;Vendor Advisory
-
https://github.com/MobSF/Mobile-Security-Framework-MobSF/issues/1211
[FEATURE] Add authentication method · Issue #1211 · MobSF/Mobile-Security-Framework-MobSF · GitHubIssue Tracking;Vendor Advisory
Jump to