Arm Compiler vulnerabilitiesRanked by how likely they are to be used.
Arm Compiler is made by Arm. We track 3 published vulnerabilities listed under that exact name, across 18 versions. None of them is on the list of flaws known to be exploited today. Arm lists newer releases under their own names, such as Arm Compiler for Embedded Fusa, so check those pages too.
We keep watching the known-exploited list.
Is Arm Compiler listed under other names? Yes.
Arm also lists Arm Compiler under more specific names, such as Arm Compiler for Embedded Fusa and Arm Compiler for Functional Safety. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which Arm Compiler vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Arm Compiler's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Arm Compiler flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 0.3%CVE-2020-24658High
Arm Compiler 5 through 5.06u6 has an error in a stack protection feature designed to help spot stack-based buffer overflows in local arrays.
- 0.2%CVE-2022-43701High
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.
- 0.2%CVE-2022-43702High
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.
Running Arm Compiler? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Arm Compiler 5 through 5.06u6 has an error in a stack protection feature designed to help spot stack-based buffer overflows in local arrays. When this feature is enabled, a protected function writes a guard value to the stack prior to (above) any vulnerable arrays in the stack. The guard value is checked for corruption on function return; corruption leads to an error-handler call. In certain circumstances, the reference value that is compared against the guard value is itself also written to the stack (after any vulnerable arrays). The reference value is written to the stack when the function runs out of registers to use for other temporary data. If both the reference value and the guard value are written to the stack, then the stack protection will fail to spot corruption when both values are overwritten with the same value. For both the reference value and the guard value to be corrupted, there would need to be both a buffer overflow and a buffer underflow in the vulnerable arrays (or some other vulnerability that causes two separated stack entries to be corrupted).
- Matched to
- Arm Compiler on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 3 published vulnerabilities listed under the name Arm Compiler, across 18 versions.
None of Arm Compiler's vulnerabilities is on the list of flaws known to be exploited today.
Arm also lists Arm Compiler under more specific names, such as Arm Compiler for Embedded Fusa and Arm Compiler for Functional Safety. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Create a Precursor Intelligence account and track Arm Compiler. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.