# CVE-2024-6051: Cross Application Scripting in Redlink SDK

> Attackers can inject local code and manipulate application views via Cross Application Scripting in the Redlink SDK.

- **Severity:** Medium 4.3 (`CVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:A/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N/AU:N/R:U/V:D/RE:L/U:Clear`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Sep 2024
- **Updated:** 3 Oct 2025
- **Also known as:** GHSA-gwqg-23x2-cww4

## What is CVE-2024-6051?

CVE-2024-6051 is a medium-severity cross-site scripting vulnerability in Vercom S.A. Redlink SDK, published on 30 Sep 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Cross Application Scripting vulnerability in Vercom S.A. Redlink SDK in specific situations allows local code injection and to manipulate the view of a vulnerable application.This issue affects Redlink SDK versions through 1.13.

Weakness: CWE-926 (Improper Export of Android Application Components)

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


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

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

## Is CVE-2024-6051 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-6051 is a medium-severity cross-site scripting vulnerability in Vercom S.A. Redlink SDK, published on 30 Sep 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-6051 in the wild and no public exploit code.

Affected product: Vercom S.A. Redlink SDK. 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-6051/ (Markdown: https://insights.sbomify.com/CVE-2024-6051/index.md)
```

## Sources

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

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