LiveActive security incident?Get immediate response
CVE Record

CVE-2017-7563: In ARM Trusted Firmware 1.3, RO memory is always executable at AArch64 Secure EL1, allowing attackers to by...

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).

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This CVE concerns a weakness in ARM Trusted Firmware 1.3 where read-only secure memory could still be executable. That undermines an intended protection boundary in low-level firmware. The public bundle does not name exploited products, active attacks, or a CVSS score, so urgency depends on confirmed firmware use.

Executive priority

Treat this as a targeted firmware exposure item. It is not supported by known exploitation evidence in the bundle, but it affects a security boundary below the operating system. Prioritize confirmation for products handling sensitive workloads or relying on ARM secure-world isolation.

Technical view

At AArch64 Secure EL1, ARM Trusted Firmware 1.3 handled execute-never protection inconsistently, using one execute-never bit where two were relevant. As a result, RO memory could remain executable and MT_EXECUTE_NEVER could be bypassed. The sources do not provide CPEs, exploit prerequisites, or patch details.

Likely exposure

Exposure is likely limited to devices or platforms that shipped ARM Trusted Firmware 1.3 or derivative secure firmware. The source bundle does not identify downstream vendors, products, chips, or operating systems. Asset teams should treat this as firmware supply-chain exposure rather than a typical application vulnerability.

Exploitation context

The CVE description says attackers could bypass an execution protection mechanism, but the bundle provides no exploit activity evidence. It is not listed as KEV. No public source in the bundle states active exploitation, weaponization, or exploitation prerequisites.

Researcher notes

The evidence is sparse: no CVSS, CWE, CPEs, exploit prerequisites, or patch identifier are included. Analysis should focus on firmware provenance, secure-world configuration, and vendor advisory mapping. Avoid assuming impact across all ARM-based devices without product-specific confirmation.

Mitigation direction

  • Check ARM Trusted Firmware Security Advisory TFV-3 for vendor guidance.
  • Inventory devices using ARM Trusted Firmware 1.3 or derivatives.
  • Request affected firmware status from OEM, SoC, and platform vendors.
  • Apply vendor-supplied secure firmware updates when available.
  • Track downstream advisories for product-specific remediation details.

Validation and detection

  • Review firmware build manifests for ARM Trusted Firmware 1.3 references.
  • Confirm AArch64 Secure EL1 use with platform or vendor documentation.
  • Check vendor advisories for CVE-2017-7563 applicability.
  • Verify deployed firmware versions after any vendor update.
  • Document systems where vendor impact status remains unknown.
Prepared
Confidence
medium
Sources
3

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2017-7563 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.