MobSF vulnerability allows SSRF due to the allow_redirects=True parameter

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2024-54000: 0.41% estimated exploitation activity in the next 30 days; percentile 35.59 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The fix for the "SSRF Vulnerability on assetlinkscheck(actname, wellknowns)" vulnerability could potentially be bypassed. Details Since the requests.get() request in the checkurl method is specified as allowredirects=True, if "https://mydomain.com/.well-known/assetlinks.json" returns a 302 redirect, subsequent requests will be sent automatically. If the redirect location is "http://192.168.1.102/user/delete/1", a request will be sent here as well. <img width="610" alt="image" src="https://github.com/MobSF/Mobile-Security-Framework-MobSF/assets/150332295/a8c9630e-3d12-441a-816c-8f5e427a5194" It will be safer to use allowredirects=False. Impact The attacker can cause the server to make a connection to internal-only services within the organization's infrastructure.

Published by the source

27 Jun 2025, 20:43 UTC

Last modified by the source

27 Jun 2025, 21:15 UTC

Source last checked

26 Oct 2026, 13:32 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-m435-9v6r-v5f6

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-m435-9v6r-v5f6

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-54000

Advisory: MobSF vulnerability allows SSRF due to the allow_redirects=True parameter
IDs: CVE-2024-54000, GHSA-m435-9v6r-v5f6
Record: https://patchnext.com/advisories/cve-2024-54000 (revision 2, source checked 26 Oct 2026, 13:32 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: mobsf 3.9.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI mobsf: affected < 3.9.7; fixed in 3.9.7

## Suggested inspection (read-only)
- `python -m pip show mobsf`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on mobsf.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-m435-9v6r-v5f6 (OSV record GHSA-m435-9v6r-v5f6 lists affected ranges: PyPI mobsf >=0 <3.9.7 (fixed))
- Verified: https://github.com/advisories/GHSA-m435-9v6r-v5f6 (GitHub-reviewed advisory GHSA-m435-9v6r-v5f6 lists affected ranges: PyPI mobsf >=0 <3.9.7)

Commands are suggestions: review each one before running it.