# CVE-2024-36842: Command injection in n/a

> Remote attackers can execute arbitrary code on Oncord+ Android infotainment systems via the ADB port, requiring immediate attention from automotive security teams.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Apr 2025
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-m875-mcc5-r6hx

## What is CVE-2024-36842?

CVE-2024-36842 is a high-severity command injection vulnerability in n/a, published on 15 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in Oncord+ Android Infotainment Systems OS Android 12, Model Hardware TS17,Hardware part Number F57L_V3.2_20220301, and Build Number PlatformVER:K24-2023/05/09-v0.01 allows a remote attacker to execute arbitrary code via the ADB port component.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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


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

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

## Is CVE-2024-36842 being exploited?

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

Public exploit code:

- CVE-2024-36842, Creating Persistent Backdoor on Oncord+ android/ios car infotaiment using malicious script! (github_poc): https://github.com/abbiy/CVE-2024-36842-Backdooring-Oncord-Android-Sterio-

## Fix prompt for AI coding agents

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

What it is: CVE-2024-36842 is a high-severity command injection vulnerability in n/a, published on 15 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-36842 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-36842/ (Markdown: https://insights.sbomify.com/CVE-2024-36842/index.md)
```

## Sources

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

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