# CVE-2024-46964: Code injection in n/a

> An attacker can execute arbitrary JavaScript code in the All Video Downloader Android app via the StartActivity component.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Nov 2024
- **Updated:** 12 Nov 2024
- **Also known as:** GHSA-xqm3-rc5r-j547

## What is CVE-2024-46964?

CVE-2024-46964 is a high-severity code injection vulnerability in n/a, published on 11 Nov 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2024-46964?


## How do I fix CVE-2024-46964?

No fix has been published for CVE-2024-46964 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-46964 being exploited?

There is no known exploitation of CVE-2024-46964 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-46964 and fix it if it is affected.

What it is: CVE-2024-46964 is a high-severity code injection vulnerability in n/a, published on 11 Nov 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-46964 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-46964/ (Markdown: https://insights.sbomify.com/CVE-2024-46964/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-46964
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-46964
- OSV: https://osv.dev/vulnerability/CVE-2024-46964

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-46964/
Summaries are generated and may contain mistakes; the official description above is the record.