Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mbedTLS 2.26.X contains multiple vulnerabilities #56071

Closed
ceolin opened this issue Mar 21, 2023 · 0 comments
Closed

mbedTLS 2.26.X contains multiple vulnerabilities #56071

ceolin opened this issue Mar 21, 2023 · 0 comments
Assignees
Labels
area: Security Security bug The issue is a bug, or the PR is fixing a bug LTS Long term release branch related priority: high High impact/importance bug
Milestone

Comments

@ceolin
Copy link
Member

ceolin commented Mar 21, 2023

Describe the bug

mbedTLS 2.26 used on Zephyr LTS contains several vulnerabilities:

https://www.cvedetails.com/cve/CVE-2021-45450/
https://www.cvedetails.com/cve/CVE-2022-35409/
https://www.cvedetails.com/cve/CVE-2022-46392/
https://www.cvedetails.com/cve/CVE-2022-46393/

Expected behavior

Use an updated version that address known issues.

Impact

Products using this version may be exploited.

Additional context

https://www.cvedetails.com/vulnerability-list/vendor_id-15698/product_id-32568/ARM-Mbed-Tls.html

@ceolin ceolin added bug The issue is a bug, or the PR is fixing a bug area: Security Security LTS Long term release branch related labels Mar 21, 2023
@ceolin ceolin added this to To do in Security features/improvements/documentation via automation Mar 21, 2023
@jgl-meta jgl-meta added the priority: high High impact/importance bug label Mar 28, 2023
@nashif nashif added this to the v2.7.4 milestone Mar 29, 2023
@cfriedt cfriedt modified the milestones: v2.7.4, v2.7.5 Mar 29, 2023
ceolin added a commit to ceolin/zephyr that referenced this issue May 8, 2023
Zephyr mbedTLS was updated to 2.28.x which is a LTS release and
address several vulnerabilities affecting 2.26 (version that used to be
used on Zephyr LTS).

Unfortunately this mbedTLS version is not compatible with TF-M and
backporting mbedTLS fixes was not a viable solution. Due this problem
we are removing TF-M module from Zephyr's LTS. One still can go and add
it to this manifest if needed, but this is no longer "officially"
supported.

More information in:
zephyrproject-rtos#56071
zephyrproject-rtos#54084

Signed-off-by: Flavio Ceolin <flavio.ceolin@intel.com>
ceolin added a commit to ceolin/zephyr that referenced this issue May 15, 2023
Zephyr mbedTLS was updated to 2.28.x which is a LTS release and
address several vulnerabilities affecting 2.26 (version that used to be
used on Zephyr LTS).

Unfortunately this mbedTLS version is not compatible with TF-M and
backporting mbedTLS fixes was not a viable solution. Due this problem
we are removing TF-M module from Zephyr's LTS. One still can go and add
it to this manifest if needed, but this is no longer "officially"
supported.

More information in:
zephyrproject-rtos#56071
zephyrproject-rtos#54084

Signed-off-by: Flavio Ceolin <flavio.ceolin@intel.com>
cfriedt pushed a commit that referenced this issue May 17, 2023
Zephyr mbedTLS was updated to 2.28.x which is a LTS release and
address several vulnerabilities affecting 2.26 (version that used to be
used on Zephyr LTS).

Unfortunately this mbedTLS version is not compatible with TF-M and
backporting mbedTLS fixes was not a viable solution. Due this problem
we are removing TF-M module from Zephyr's LTS. One still can go and add
it to this manifest if needed, but this is no longer "officially"
supported.

More information in:
#56071
#54084

Signed-off-by: Flavio Ceolin <flavio.ceolin@intel.com>
@ceolin ceolin closed this as completed May 19, 2023
Security features/improvements/documentation automation moved this from To do to Done May 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: Security Security bug The issue is a bug, or the PR is fixing a bug LTS Long term release branch related priority: high High impact/importance bug
Projects
No open projects
Development

No branches or pull requests

4 participants