# CVE-2022-36602: Code injection in n/a

> Remote attackers can execute arbitrary code on InnoSilicon A10 devices via the setPlatformAPI function.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Sep 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-7537-8338-g978

## What is CVE-2022-36602?

CVE-2022-36602 is a high-severity code injection vulnerability in n/a, published on 1 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

InnoSilicon A10 a10_20200924_120556 was discovered to contain a remote code execution (RCE) vulnerability in the setPlatformAPI function.

## Which versions are affected by CVE-2022-36602?

It affects 1 product.


Products: Innosilicon A10 Firmware.

## How do I fix CVE-2022-36602?

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

## Is CVE-2022-36602 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-36602 and fix it if it is affected.

What it is: CVE-2022-36602 is a high-severity code injection vulnerability in n/a, published on 1 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-36602 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-2022-36602/ (Markdown: https://insights.sbomify.com/CVE-2022-36602/index.md)
```

## Sources

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

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