← Back
CVE-2024-43399
Path Traversal in mobsf (CVE-2024-43399)
Summary
path traversal in mobsf (CVE-2024-43399). Successful exploitation can lead to full system takeover. Exploitable via ``poc.VULN``. Mitigation: upgrade to `4.0.7` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-43399** has been found in mobsf.
Attackers can target a specific entry point like ``poc.VULN`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
What to do: upgrade mobsf to **4.0.7** or later.
If unsure, ask your IT team or search "mobsf CVE-2024-43399" on the vendor's site.
CVE-2024-43399 (mobsf) — CWE-22 /
Attack vector: remote (network-reachable)
Attack surface: `poc.VULN` / `poc.a`
Patched: `4.0.7` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**Path traversal** (CWE-22) exists in mobsf. Attackers reach the vulnerable code path via ``poc.VULN`` without authentication.
📍 Affected scope
mobsf — . Attack surface: `poc.VULN` / `poc.a`.
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **4.0.7**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'mobsf' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'mobsf' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `mobsf` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade mobsf to 4.0.7ステージング環境で 4.0.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
mobsf
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.0.7"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-43399
- advisory https://github.com/advisories/GHSA-4hh3-vj32-gr6j
- package https://github.com/MobSF/Mobile-Security-Framework-MobSF
- package https://pypi.org/project/mobsf
- web https://github.com/MobSF/Mobile-Security-Framework-MobSF/security/advisories/GHSA-4hh3-vj32-gr6j
- web https://github.com/MobSF/Mobile-Security-Framework-MobSF/commit/cc625fe8430f3437a473e82aa2966d100a4dc883