Code InjectionWeakness · CWE-94

CVE-2024-46960

HIGH · 8.8 CVSS v3.1 Published 2024-11-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
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 ASD com.rocks.video.downloader (aka HD Video Downloader All Format) application through 7.0.129 for Android allows an attacker to execute arbitrary JavaScript code via the com.rocks.video.downloader.MainBrowserActivity 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 HD Video Downloader All Format (com.rocks.video.downloader) through version 7.0.129 contains a WebView component (MainBrowserActivity) that allows arbitrary JavaScript code execution. This vulnerability likely stems from improper WebView configuration, such as enabled JavaScript interfaces without proper input validation, enabling an attacker to inject and execute malicious JavaScript in the context of the WebView.

MitigationDisable JavaScript in WebViews unless strictly required, implement proper WebView settings (setJavaScriptEnabled(false)), remove unnecessary JavaScript interfaces, and add input validation for any web content loaded.

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
High

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

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. Check if the vulnerable app is installed
    Query the package manager or use an app inventory tool to detect if the package name com.rocks.video.downloader exists on the device
    Affected if The app with package name com.rocks.video.downloader is installed on the device
  2. Determine the installed version
    Retrieve the version code or version name of com.rocks.video.downloader from the package manager and compare it against 7.0.129
    Affected if The installed version is 7.0.129 or any earlier version
  3. Extract and inspect the APK
    Obtain the APK file for the installed version and use a reverse engineering tool (such as jadx or apktool) to decompile and examine the MainBrowserActivity class
    Affected if The APK can be extracted and contains the MainBrowserActivity component
  4. Review WebView JavaScript settings
    In the decompiled MainBrowserActivity source, search for WebView initialization code and check if setJavaScriptEnabled(true) is called, or if @JavascriptInterface annotations are present on methods
    Affected if JavaScript is enabled in the WebView configuration (setJavaScriptEnabled(true)) and JavaScript interface methods are exposed without validation

A user is affected if the HD Video Downloader All Format app (com.rocks.video.downloader) is installed at version 7.0.129 or lower and the MainBrowserActivity WebView has JavaScript enabled with exposed interfaces.

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 WebViews unless strictly required, implement proper WebView settings (setJavaScriptEnabled(false)), remove unnecessary JavaScript interfaces, and add input validation for any web content loaded.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-46960 — 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-46960 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