Code InjectionWeakness · CWE-94

CVE-2024-46964

HIGH · 8.1 CVSS v3.1 Published 2024-11-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
88/100
Remediation priority · High
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The com.video.downloader.all (aka All Video Downloader) application through 11.28 for Android allows an attacker to execute arbitrary JavaScript code via the com.video.downloader.all.StartActivity component.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The All Video Downloader Android app (versions through 11.28) exposes the StartActivity component which is exported and accessible externally. This Activity contains a WebView with JavaScript execution enabled that can be triggered via intent parameters, allowing an attacker to execute arbitrary JavaScript code in the context of the WebView. This could enable theft of cookies, session tokens, or manipulation of WebView content.

MitigationSet android:exported="false" on the StartActivity in AndroidManifest.xml, or add signature-level permission requirements. If JavaScript execution in WebView is required, validate and sanitize all intent extras before passing to WebView.loadUrl() or evaluateJavascript().

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if All Video Downloader is installed
    Check installed apps on the Android device for 'All Video Downloader' or the package name (typically com.allvideodownloader or similar). Use 'adb shell pm list packages' or check device settings.
    Affected if The All Video Downloader app is installed on the device.
  2. Check the installed app version
    Run 'adb shell dumpsys package <package_name>' to retrieve the version info, or view the app details in the device settings under Apps > All Video Downloader. Compare the version number to the affected range (versions through 11.28).
    Affected if The installed version is 11.28 or any earlier version.
  3. Inspect AndroidManifest.xml for exported StartActivity
    Decompile the APK (using apktool or similar) and examine AndroidManifest.xml. Look for the activity with name 'StartActivity' and check if android:exported="true" is set, or if exported is not explicitly set to false.
    Affected if The StartActivity has android:exported="true" or lacks an explicit android:exported="false" setting.
  4. Verify WebView JavaScript execution is enabled
    Decompile the APK and examine the StartActivity.smali or Java source. Search for WebView setup code and verify that setJavaScriptEnabled(true) is called, or that the WebView configuration enables JavaScript.
    Affected if The WebView in StartActivity has JavaScript execution enabled (setJavaScriptEnabled(true)).
  5. Check for unsafe intent parameter handling
    In the StartActivity source/smali, examine how intent extras are processed. Look for code that passes intent parameters directly to WebView.loadUrl() or evaluateJavascript() without validation.
    Affected if Intent extras are passed directly to WebView methods without sanitization, allowing external intent triggers to inject JavaScript.

A user is affected if All Video Downloader version 11.28 or earlier is installed AND the StartActivity is exported AND the WebView has JavaScript enabled AND intent parameters are not validated before being used in WebView calls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Set android:exported="false" on the StartActivity in AndroidManifest.xml, or add signature-level permission requirements. If JavaScript execution in WebView is required, validate and sanitize all intent extras before passing to WebView.loadUrl() or evaluateJavascript().

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-46964 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-46964 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data