Hi,
I'm seeing this warning when running cmake from a conan pkg: `/home/brian/.conan/data/cmake/3.21.3-0/library-msp/ga/package/be241241e9d4718e5bab4eb33935bbb69606bb0c/bin/cmake -S . -B build -DTFM_PLATFORM=arm/mps2/an521`. Does anyone know how to fix it? I see the language is set by `project("Trusted Firmware M" VERSION ${TFM_VERSION} LANGUAGES C CXX ASM)`.
Per-partition files done:
CMake Warning (dev) at /home/brian/.conan/data/cmake/3.21.3-0/library-msp/ga/package/be241241e9d4718e5bab4eb33935bbb69606bb0c/share/cmake-3.21/Modules/GNUInstallDirs.cmake:236 (message):
Unable to determine default CMAKE_INSTALL_LIBDIR directory because no
target architecture is known. Please enable at least one language before
including GNUInstallDirs.
Call Stack (most recent call first):
build/lib/ext/mbedcrypto-src/CMakeLists.txt:42 (include)
This warning is for project developers. Use -Wno-dev to suppress it.
Regards,
Brian Quach
SimpleLink MCU
Texas Instruments Inc.
12500 TI Blvd, MS F-4000
Dallas, TX 75243
214-479-4076
Hello,
This email is to notify you of 3 new security vulnerabilities affecting Trusted Firmware-M (TF-M).
1. Pre-auth OOB write in RSE SFCP handshake hijacks BL1 boot-ROM control flow
Some RSE configurations place nodes in a trusted subnet whose links are initially untrusted, so the SFCP implementation performs a handshake before normal traffic is protected with the negotiated session key.
Advisory: https://trustedfirmware-m.readthedocs.io/en/latest/security/security_adviso…
Fix: https://review.trustedfirmware.org/plugins/gitiles/TF-M/trusted-firmware-m/…
1. Plaintext SFCP packet on RSE returns delegated-attestation private key
The platform expects that the RSEs in the system are members of the trusted subnet and therefore use encrypted communications. This is not enforced on the "non-interrupt driven" receive code path for sfcp_receive_msg. Therefore, external RSEs in the system could send unencrypted packets which would be successfully received.
Advisory: https://trustedfirmware-m.readthedocs.io/en/latest/security/security_adviso…
Fix: https://review.trustedfirmware.org/plugins/gitiles/TF-M/trusted-firmware-m/…
1. OOB flash write in Corstone-1000 update bricks the secure enclave
The Corstone-1000 FWU bootloader backend writes update payload blocks directly to flash through ProgramData().
The write address is calculated from the target image partition base plus the number of image bytes already received. Without validating this calculated range against the flash address space and the selected update partition size, a sequence of FWU writes can extend past the end of the intended partition.
Advisory: https://trustedfirmware-m.readthedocs.io/en/latest/security/security_adviso…
Fix: https://review.trustedfirmware.org/plugins/gitiles/TF-M/trusted-firmware-m/…
If you have any questions or comments, please let us know.
Best regards,
Anton
on behalf of the TF-M Security Team
Hello TF-M Community,
I'd like to upgrade the default CMake version in TF-M to 4.3.5.
Please let me know if you have any objections or foresee compatibility issues with your development environment or downstream projects. If there are no objections by Sep 21, I'll proceed with the upgrade.
Thanks,
Anton
