# CVE-2022-43702: Incomplete verification of installation file signature

> Attackers can execute malicious code by modifying installer files if directory permissions are not restrictive, affecting Arm development tools.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jul 2023
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-g3h3-xh77-5fcf

## What is CVE-2022-43702?

CVE-2022-43702 is a high-severity code injection vulnerability in Arm Compiler 5 (AC5), Arm Compiler for Embedded 6 (AC6), Fast Models (FM), Arm Compiler for Embedded FuSA (ACEF), Arm Development Studio (ADS), Arm Forge (AF), Arm Mobile Studio (AMS), DS-5 Development Studio, Fast Models (FM), GNU Toolchain (GT), Keil MDK (KMDK), Mbed Studio (MS), published on 27 Jul 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

When the directory containing the installer does not have sufficiently restrictive file permissions, an attacker can modify (or replace) the installer to execute malicious code.

Weakness: CWE-276 (Incorrect Default Permissions), CWE-284 (Improper Access Control)

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

It affects 6 products.


Products: Arm Arm Compiler, Arm Arm Compiler for Embedded Fusa, Arm Arm Compiler for Functional Safety, Arm Arm Development Studio, Arm Ds Development Studio, Arm Fast Models.

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

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

## Is CVE-2022-43702 being exploited?

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

## Other vulnerabilities in Arm Compiler 5 (AC5), Arm Compiler for Embedded 6 (AC6), Fast Models (FM), Arm Compiler for Embedded FuSA (ACEF), Arm Development Studio (ADS), Arm Forge (AF), Arm Mobile Studio (AMS), DS-5 Development Studio, Fast Models (FM), GNU Toolchain (GT), Keil MDK (KMDK), Mbed Studio (MS)

- [CVE-2022-43701](https://insights.sbomify.com/CVE-2022-43701/): Insecure directory permissions on installer files (high 7.8)
- [CVE-2020-24658](https://insights.sbomify.com/CVE-2020-24658/): Security feature bypass in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-43702 is a high-severity code injection vulnerability in Arm Compiler 5 (AC5), Arm Compiler for Embedded 6 (AC6), Fast Models (FM), Arm Compiler for Embedded FuSA (ACEF), Arm Development Studio (ADS), Arm Forge (AF), Arm Mobile Studio (AMS), DS-5 Development Studio, Fast Models (FM), GNU Toolchain (GT), Keil MDK (KMDK), Mbed Studio (MS), published on 27 Jul 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-43702 in the wild and no public exploit code.

Affected product: Arm Compiler 5 (AC5), Arm Compiler for Embedded 6 (AC6), Fast Models (FM), Arm Compiler for Embedded FuSA (ACEF), Arm Development Studio (ADS), Arm Forge (AF), Arm Mobile Studio (AMS), DS-5 Development Studio, Fast Models (FM), GNU Toolchain (GT), Keil MDK (KMDK), Mbed Studio (MS). 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-43702/ (Markdown: https://insights.sbomify.com/CVE-2022-43702/index.md)
```

## Sources

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

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