CVE-2022-43701: Insecure directory permissions on installer files

Published Jul 27, 2023
·
Updated

When the installation directory does not have sufficiently restrictive file permissions, an attacker can modify files in the installation directory to cause execution of malicious code.

Affected Software

12 affected components
Arm Arm Compiler>=5.00<=5.06
Arm Arm Compiler>=6.00<6.20
Arm Arm Compiler For Embedded Fusa=6.16
Arm Arm Compiler For Functional Safety=6.6
Arm Arm Development Studio
Arm Arm Mobile Studio
Arm Ds Development Studio>=5.0.0<=5.29.3
Arm Fast Models
Arm Gnu Toolchain
Arm Keil Mdk
Arm Linaro Forge<22.1
Arm Mbed Studio

Event History

Jul 27, 2023
CVE Published
via MITRE·09:28 PM
Data Sourced
via MITRE·09:28 PM
DescriptionWeakness
Data Sourced
10:15 PM
Description
Data Sourced
via NVD·10:15 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is CVE-2022-43701?

CVE-2022-43701 is a vulnerability that occurs when the installation directory does not have sufficiently restrictive file permissions, allowing an attacker to modify files and execute malicious code.

2

Which software is affected by CVE-2022-43701?

The Arm Arm Compiler versions 5.00 to 5.06, Arm Arm Compiler versions 6.00 to 6.20, Arm Arm Compiler For Embedded Fusa version 6.16, Arm Arm Compiler For Functional Safety version 6.6, Arm Arm Development Studio, Arm Arm Mobile Studio, Arm Ds Development Studio versions 5.0.0 to 5.29.3, Arm Fast Models, Arm Gnu Toolchain, Arm Keil Mdk, Arm Linaro Forge versions up to 22.1, and Arm Mbed Studio are affected by CVE-2022-43701.

3

What is the severity of CVE-2022-43701?

CVE-2022-43701 has a severity rating of 7.8 (high).

4

How does CVE-2022-43701 impact security?

CVE-2022-43701 can allow an attacker to modify files in the installation directory and execute malicious code, potentially compromising the security of the affected software.

5

How can I mitigate CVE-2022-43701?

To mitigate CVE-2022-43701, ensure that the installation directory has sufficiently restrictive file permissions to prevent unauthorized modification of files.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203