Code InjectionWeakness · CWE-94

CVE-2024-46966

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 Ikhgur mn.ikhgur.khotoch (aka Video Downloader Pro & Browser) application through 1.0.42 for Android allows an attacker to execute arbitrary JavaScript code via the mn.ikhgur.khotoch.MainActivity 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 'Video Downloader Pro & Browser' (mn.ikhgur.khotoch) through version 1.0.42 contains a vulnerability in its MainActivity component that allows arbitrary JavaScript code execution. This is typically caused by insecure WebView implementation where the app loads untrusted content or allows user-supplied data to be rendered with JavaScript execution enabled, enabling attackers to inject and execute malicious scripts.

MitigationUpdate to a patched version of the application once released by the vendor; as an interim measure, avoid using the application's browsing features with untrusted sources. For developers, implement proper input validation and disable JavaScript execution in WebViews unless absolutely necessary and only for trusted content.

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. Verify the application is installed
    Check if the Android app with package name 'mn.ikhgur.khotoch' is installed. Use 'adb shell pm list packages | grep mn.ikhgur.khotoch' or check in Settings > Apps for 'Video Downloader Pro & Browser'
    Affected if The package mn.ikhgur.khotoch is present on the device
  2. Determine the installed version
    Obtain the version name of the installed app. Run 'adb shell dumpsys package mn.ikhgur.khotoch' and locate the versionName field, or view it in the app info screen under Settings > Apps > Video Downloader Pro & Browser
    Affected if The version is 1.0.42 or any version below it (through 1.0.42)
  3. Confirm the app has browsing functionality
    This is inherent to the app description - Video Downloader Pro & Browser includes a built-in browser. The vulnerability exists in the MainActivity WebView component that handles web content rendering
    Affected if The app is installed at a vulnerable version and includes WebView-based browsing features

If the app 'Video Downloader Pro & Browser' (package mn.ikhgur.khotoch) is installed at version 1.0.42 or lower, the environment is affected by this arbitrary JavaScript execution vulnerability in the MainActivity WebView component.

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

Update to a patched version of the application once released by the vendor; as an interim measure, avoid using the application's browsing features with untrusted sources. For developers, implement proper input validation and disable JavaScript execution in WebViews unless absolutely necessary and only for trusted content.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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