# CVE-2017-7563: Security feature bypass in n/a

> Attackers can bypass MT_EXECUTE_NEVER protection in ARM Trusted Firmware due to inconsistent execute-never bit handling, compromising secure memory integrity.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-26gw-4gmp-qgf3

## What is CVE-2017-7563?

CVE-2017-7563 is a high-severity vulnerability in n/a, published on 7 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In ARM Trusted Firmware 1.3, RO memory is always executable at AArch64 Secure EL1, allowing attackers to bypass the MT_EXECUTE_NEVER protection mechanism. This issue occurs because of inconsistency in the number of execute-never bits (one bit versus two bits).

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2017-7563?

It affects 1 product.


Products: Trustedfirmware Trusted Firmware-A.

## How do I fix CVE-2017-7563?

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

## Is CVE-2017-7563 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-15031](https://insights.sbomify.com/CVE-2017-15031/): Information disclosure in n/a (high 7.5)
- [CVE-2017-7564](https://insights.sbomify.com/CVE-2017-7564/): Denial of service in n/a (high 7.5)
- [CVE-2022-47630](https://insights.sbomify.com/CVE-2022-47630/): Information disclosure in n/a (high 7.4)
- [CVE-2017-9607](https://insights.sbomify.com/CVE-2017-9607/): Integer overflow in n/a (high 7.0)
- [CVE-2018-19440](https://insights.sbomify.com/CVE-2018-19440/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-7563 and fix it if it is affected.

What it is: CVE-2017-7563 is a high-severity vulnerability in n/a, published on 7 Jun 2017. 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-2017-7563 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-2017-7563/ (Markdown: https://insights.sbomify.com/CVE-2017-7563/index.md)
```

## Sources

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

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