2. Security Handling

2.1. Security Disclosures

We disclose all security vulnerabilities we find, or are advised about, that are relevant to Trusted Firmware-A. We encourage responsible disclosure of vulnerabilities and inform users as best we can about all possible issues.

We disclose TF-A vulnerabilities as Security Advisories, all of which are listed at the bottom of this page. Any new ones will, additionally, be announced as issues in the project’s issue tracker with the security-advisory tag. You can receive notification emails for these by watching the “Trusted Firmware-A” project at https://developer.trustedfirmware.org/.

2.2. Found a Security Issue?

Although we try to keep TF-A secure, we can only do so with the help of the community of developers and security researchers.

If you think you have found a security vulnerability, please do not report it in the issue tracker. Instead send an email to trusted-firmware-security@arm.com

Please include:

  • Trusted Firmware-A version (or commit) affected

  • A description of the concern or vulnerability

  • Details on how to replicate the vulnerability, including:

    • Configuration details

    • Proof of concept exploit code

    • Any additional software or tools required

We recommend using this PGP/GPG key for encrypting the information. This key is also available at http://keyserver.pgp.com and LDAP port 389 of the same server.

The fingerprint for this key is:

1309 2C19 22B4 8E87 F17B FE5C 3AB7 EFCB 45A0 DFD0

If you would like replies to be encrypted, please provide your public key.

Please give us the time to respond to you and fix the vulnerability before going public. We do our best to respond and fix any issues quickly. We also need to ensure providers of products that use TF-A have a chance to consider the implications of the vulnerability and its remedy.

Afterwards, we encourage you to write-up your findings about the TF-A source code.

2.3. Attribution

We will name and thank you in the Change Log & Release Notes distributed with the source code and in any published security advisory.

2.4. Security Advisories

ID

Title

Advisory TFV-1 (CVE-2016-10319)

Malformed Firmware Update SMC can result in copy of unexpectedly large data into secure memory

Advisory TFV-2 (CVE-2017-7564)

Enabled secure self-hosted invasive debug interface can allow normal world to panic secure world

Advisory TFV-3 (CVE-2017-7563)

RO memory is always executable at AArch64 Secure EL1

Advisory TFV-4 (CVE-2017-9607)

Malformed Firmware Update SMC can result in copy or authentication of unexpected data in secure memory in AArch32 state

Advisory TFV-5 (CVE-2017-15031)

Not initializing or saving/restoring PMCR_EL0 can leak secure world timing information

Advisory TFV-6 (CVE-2017-5753, CVE-2017-5715, CVE-2017-5754)

Trusted Firmware-A exposure to speculative processor vulnerabilities using cache timing side-channels

Advisory TFV-7 (CVE-2018-3639)

Trusted Firmware-A exposure to cache speculation vulnerability Variant 4

Advisory TFV-8 (CVE-2018-19440)

Not saving x0 to x3 registers can leak information from one Normal World SMC client to another


Copyright (c) 2019, Arm Limited. All rights reserved.