CVE-2024-46962
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 · uneditedThe SYQ com.downloader.video.fast (aka Master Video Downloader) application through 2.0 for Android allows an attacker to execute arbitrary JavaScript code via the com.downloader.video.fast.SpeedMainAct 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 confidenceThe Master Video Downloader Android application (versions up to 2.0) contains an improper input validation vulnerability in the SpeedMainAct component. This component, likely a WebView, fails to properly sanitize or restrict JavaScript input, allowing an attacker to inject and execute arbitrary JavaScript code within the application's context.
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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Master Video Downloader app is installedCheck installed apps on the Android device for 'Master Video Downloader' or the package name associated with it. Use 'adb shell pm list packages' or check via device settings.Affected if The app is present on the device.
-
Check the installed app versionRun 'adb shell dumpsys package <package_name>' to retrieve the version info, or inspect the APK metadata. Compare the version number to the affected range (versions up to and including 2.0).Affected if The installed version is 2.0 or lower.
-
Locate the SpeedMainAct componentUse 'adb shell dumpsys package <package_name>' to list all components, or decompile the APK and inspect the AndroidManifest.xml for the SpeedMainAct activity.Affected if The SpeedMainAct component exists in the application.
-
Verify if JavaScript is enabled in the WebView configurationDecompile the APK and inspect the SpeedMainAct source code for WebView settings. Specifically look for 'setJavaScriptEnabled(true)' or 'WebSettings.setJavaScriptEnabled(true)' calls.Affected if JavaScript execution is enabled in the WebView within SpeedMainAct.
-
Check for input validation on JavaScript execution pointsReview the SpeedMainAct source code for any addJavascriptInterface calls or evaluateJavascript usage. Inspect whether input parameters passed to these methods undergo sanitization or allowlisting before execution.Affected if No input validation or allowlisting is implemented on JavaScript input to the WebView.
A user is affected if Master Video Downloader version 2.0 or lower is installed, the SpeedMainAct component exists, and JavaScript execution is enabled without proper input validation on the JavaScript execution points.
Generated from the published advisory. Verify against your own configuration.
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 dataDisable JavaScript execution in the WebView configuration within the SpeedMainAct component, or implement strict input validation/allowlisting for any JavaScript that must be executed. If JavaScript execution is not required for core functionality, it should be disabled entirely.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-46962 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-46962 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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