CVE-2017-7563: High severity Arm ARM Trusted Firmware vulnerability

Published Jun 7, 2017
·
Updated

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

Affected Software

2 affected components
Arm ARM Trusted Firmware<=1.3
TrustedFirmware Trusted Firmware-a<=1.3

Event History

Jun 7, 2017
CVE Published
via MITRE·03:00 PM
Data Sourced
via MITRE·03:00 PM
Description
Data Sourced
via NVD·03:29 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 the severity of CVE-2017-7563?

CVE-2017-7563 is classified as a high-severity vulnerability due to its potential to allow unauthorized code execution in a secure environment.

2

How do I fix CVE-2017-7563?

To mitigate CVE-2017-7563, update the ARM Trusted Firmware to a version later than 1.3, which addresses the execute-never bit inconsistency.

3

What are the potential impacts of CVE-2017-7563?

CVE-2017-7563 can lead to exploits that bypass the MT_EXECUTE_NEVER protection and allow attackers to execute code in read-only memory.

4

Which versions of ARM Trusted Firmware are affected by CVE-2017-7563?

All versions of ARM Trusted Firmware up to and including 1.3 are affected by CVE-2017-7563.

5

Is there a workaround for CVE-2017-7563 if I cannot update?

No reliable workaround is available for CVE-2017-7563; the recommended action is to upgrade to a patched version of the firmware.

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