dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-46965

MEDIUM · 5.4 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 →
61/100
Remediation priority · Elevated
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 DS allvideo.downloader.browser (aka Fast Video Downloader: Browser) application through 1.6-RC1 for Android allows an attacker to execute arbitrary JavaScript code via the allvideo.downloader.browser.DefaultBrowserActivity 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 · moderate confidence

The Android application's DefaultBrowserActivity component (a WebView-based browser) allows execution of arbitrary JavaScript code due to improper WebView configuration. This is a Cross-Site Scripting (XSS) vulnerability in the embedded browser that fails to sanitize or properly sandbox JavaScript execution from web content.

MitigationDisable JavaScript in the WebView unless explicitly required, implement proper content validation/sandboxing, or update to a patched version when available. Users should avoid navigating to untrusted websites within the application.

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/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 application with DefaultBrowserActivity component
    Use a package inspector (like 'adb shell pm list packages' or a rooted device analyzer) to identify which Android application contains the DefaultBrowserActivity component. Check the AndroidManifest.xml or use 'dumpsys package <pkg>' for activities.
    Affected if The device has an installed application that exports or uses a component named DefaultBrowserActivity acting as a WebView-based browser
  2. Verify WebView is used for browser functionality
    Decompile or analyze the application APK. Inspect the DefaultBrowserActivity source code to confirm it uses android.webkit.WebView for rendering web content.
    Affected if DefaultBrowserActivity implements android.webkit.WebView to load and display web pages
  3. Check WebView JavaScript enablement
    Inspect the WebView settings in DefaultBrowserActivity code. Look for WebSettings.setJavaScriptEnabled(true) calls without corresponding setJavaScriptBridgeEnabled(false) or content URL validation.
    Affected if WebView has JavaScript enabled (setJavaScriptEnabled(true)) and lacks proper sandboxing configuration like setAllowFileAccess(false), setAllowContentAccess(false), or URL validation before loadUrl() calls
  4. Confirm lack of input sanitization on loaded URLs
    Review the DefaultBrowserActivity code path from user input (Intent extras, URL parameters) to WebView.loadUrl() to see if any sanitization or validation occurs on the URL before loading.
    Affected if The application passes user-controlled URLs directly to WebView.loadUrl() without validating that the URL scheme is safe (e.g., http/https) or without sanitizing potentially malicious content
  5. Verify no XSS mitigation in WebView client
    Check if WebViewClient or WebChromeClient is overridden to implement ContentSecurityPolicy, onJsAlert handling, or other XSS guards. Look for missing shouldOverrideUrlLoading validation.
    Affected if The WebView lacks custom WebViewClient callbacks that implement URL validation or XSS filtering before page rendering

A user is affected if their Android device runs an application containing a DefaultBrowserActivity WebView component with JavaScript enabled and no URL validation or sandboxing implemented in the code path from external input to WebView load.

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

Disable JavaScript in the WebView unless explicitly required, implement proper content validation/sandboxing, or update to a patched version when available. Users should avoid navigating to untrusted websites within the application.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-46965 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