blob: 516eb98d76b629b8f310184332bf41be73210b4e [file] [log] [blame]
Paul Beesley8aa05052019-03-07 15:47:15 +00001Security Handling
2=================
Paul Beesley0c6be932019-03-05 17:19:37 +00003
Joel Hutton4fe91232019-02-25 15:18:56 +00004Security Disclosures
5--------------------
6
John Tsichritzis55f14052019-05-21 10:37:55 +01007We disclose all security vulnerabilities we find, or are advised about, that are
8relevant to Trusted Firmware-A. We encourage responsible disclosure of
Joel Hutton4fe91232019-02-25 15:18:56 +00009vulnerabilities and inform users as best we can about all possible issues.
10
John Tsichritzis55f14052019-05-21 10:37:55 +010011We disclose TF-A vulnerabilities as Security Advisories, all of which are listed
12at the bottom of this page. Any new ones will, additionally, be announced as
13issues in the project's `issue tracker`_ with the ``security-advisory`` tag. You
14can receive notification emails for these by watching the "Trusted Firmware-A"
15project at https://developer.trustedfirmware.org/.
Joel Hutton4fe91232019-02-25 15:18:56 +000016
17Found a Security Issue?
18-----------------------
19
John Tsichritzis55f14052019-05-21 10:37:55 +010020Although we try to keep TF-A secure, we can only do so with the help of the
Joel Hutton4fe91232019-02-25 15:18:56 +000021community of developers and security researchers.
22
Sandrine Bailleux1367cc12020-06-22 12:11:47 +020023If you think you have found a security vulnerability, please **do not** report
24it in the `issue tracker`_. Instead, please follow the `TrustedFirmware.org
25security incident process`_. One of the goals of this process is to ensure
26providers of products that use TF-A have a chance to consider the implications
27of the vulnerability and its remedy before it is made public. As such, please
28follow the disclosure plan outlined in the process. We do our best to respond
29and fix any issues quickly.
Joel Hutton4fe91232019-02-25 15:18:56 +000030
John Tsichritzis55f14052019-05-21 10:37:55 +010031Afterwards, we encourage you to write-up your findings about the TF-A source
32code.
Joel Hutton4fe91232019-02-25 15:18:56 +000033
34Attribution
35-----------
36
Sandrine Bailleux1367cc12020-06-22 12:11:47 +020037We will name and thank you in the :ref:`Change Log & Release Notes` distributed
38with the source code and in any published security advisory.
Joel Hutton4fe91232019-02-25 15:18:56 +000039
40Security Advisories
41-------------------
42
43+-----------+------------------------------------------------------------------+
44| ID | Title |
45+===========+==================================================================+
Paul Beesley34760952019-04-12 14:19:42 +010046| |TFV-1| | Malformed Firmware Update SMC can result in copy of unexpectedly |
Joel Hutton4fe91232019-02-25 15:18:56 +000047| | large data into secure memory |
48+-----------+------------------------------------------------------------------+
Paul Beesley34760952019-04-12 14:19:42 +010049| |TFV-2| | Enabled secure self-hosted invasive debug interface can allow |
Joel Hutton4fe91232019-02-25 15:18:56 +000050| | normal world to panic secure world |
51+-----------+------------------------------------------------------------------+
Paul Beesley34760952019-04-12 14:19:42 +010052| |TFV-3| | RO memory is always executable at AArch64 Secure EL1 |
Joel Hutton4fe91232019-02-25 15:18:56 +000053+-----------+------------------------------------------------------------------+
Paul Beesley34760952019-04-12 14:19:42 +010054| |TFV-4| | Malformed Firmware Update SMC can result in copy or |
Joel Hutton4fe91232019-02-25 15:18:56 +000055| | authentication of unexpected data in secure memory in AArch32 |
56| | state |
57+-----------+------------------------------------------------------------------+
Paul Beesley34760952019-04-12 14:19:42 +010058| |TFV-5| | Not initializing or saving/restoring PMCR_EL0 can leak secure |
Joel Hutton4fe91232019-02-25 15:18:56 +000059| | world timing information |
60+-----------+------------------------------------------------------------------+
Paul Beesley34760952019-04-12 14:19:42 +010061| |TFV-6| | Trusted Firmware-A exposure to speculative processor |
Joel Hutton4fe91232019-02-25 15:18:56 +000062| | vulnerabilities using cache timing side-channels |
63+-----------+------------------------------------------------------------------+
Paul Beesley34760952019-04-12 14:19:42 +010064| |TFV-7| | Trusted Firmware-A exposure to cache speculation vulnerability |
Joel Hutton4fe91232019-02-25 15:18:56 +000065| | Variant 4 |
66+-----------+------------------------------------------------------------------+
Paul Beesley34760952019-04-12 14:19:42 +010067| |TFV-8| | Not saving x0 to x3 registers can leak information from one |
Joel Hutton4fe91232019-02-25 15:18:56 +000068| | Normal World SMC client to another |
69+-----------+------------------------------------------------------------------+
70
John Tsichritzis55f14052019-05-21 10:37:55 +010071.. _issue tracker: https://developer.trustedfirmware.org/project/board/1/
Paul Beesley34760952019-04-12 14:19:42 +010072
73.. |TFV-1| replace:: :ref:`Advisory TFV-1 (CVE-2016-10319)`
74.. |TFV-2| replace:: :ref:`Advisory TFV-2 (CVE-2017-7564)`
75.. |TFV-3| replace:: :ref:`Advisory TFV-3 (CVE-2017-7563)`
76.. |TFV-4| replace:: :ref:`Advisory TFV-4 (CVE-2017-9607)`
77.. |TFV-5| replace:: :ref:`Advisory TFV-5 (CVE-2017-15031)`
78.. |TFV-6| replace:: :ref:`Advisory TFV-6 (CVE-2017-5753, CVE-2017-5715, CVE-2017-5754)`
79.. |TFV-7| replace:: :ref:`Advisory TFV-7 (CVE-2018-3639)`
80.. |TFV-8| replace:: :ref:`Advisory TFV-8 (CVE-2018-19440)`
81
Sandrine Bailleux1367cc12020-06-22 12:11:47 +020082.. _TrustedFirmware.org security incident process: https://developer.trustedfirmware.org/w/collaboration/security_center/
83
Paul Beesley34760952019-04-12 14:19:42 +010084--------------
85
Sandrine Bailleux1367cc12020-06-22 12:11:47 +020086*Copyright (c) 2019-2020, Arm Limited. All rights reserved.*