Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.3amended

SSRF Vulnerability on assetlinks_check(act_name, well_knowns)

CVE-2024-29190GHSA-wfgj-wrgh-h3r3

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (mobsfscan 0.3.8; mobsf 3.9.7), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI mobsfscan

    Affected
    < 0.3.8
    Fixed in
    0.3.8

  • PyPI mobsf

    Affected
    < 3.9.7
    Fixed in
    3.9.7

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
EPSS
  • CVE-2024-29190: 0.72% estimated exploitation activity in the next 30 days; percentile 53.89 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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: 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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-wfgj-wrgh-h3r3

  2. Revision 2 · amended ·

    Amended from osv record PYSEC-2024-257

  3. Revision 1 · created ·

    Published from osv record GHSA-wfgj-wrgh-h3r3

Agent brief

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

# Patch Next advisory brief: CVE-2024-29190

Advisory: SSRF Vulnerability on assetlinks_check(act_name, well_knowns)
IDs: CVE-2024-29190, GHSA-wfgj-wrgh-h3r3
Record: https://patchnext.com/advisories/cve-2024-29190 (revision 3, 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.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: mobsfscan 0.3.8; mobsf 3.9.7. A vendor fix does not mean a deployment is fixed.

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

## Suggested inspection (read-only)
- `python -m pip show mobsfscan`: prints the installed version. Run with the environment that serves production active.
- `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 mobsfscan, 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-wfgj-wrgh-h3r3 (OSV record GHSA-wfgj-wrgh-h3r3 lists affected ranges: PyPI mobsfscan >=0 <0.3.8 (fixed))
- Verified: https://osv.dev/vulnerability/PYSEC-2024-257 (OSV record PYSEC-2024-257 lists affected ranges: PyPI mobsf >=0 <3.9.7 (fixed))
- Verified: https://github.com/advisories/GHSA-wfgj-wrgh-h3r3 (GitHub-reviewed advisory GHSA-wfgj-wrgh-h3r3 lists affected ranges: PyPI mobsfscan >=0 <0.3.8)

Commands are suggestions: review each one before running it.

Loading voting…