mbedtls - Debian Package Tracker

general

source: mbedtls (main)
version: 2.16.9-0.1
maintainer: James Cowgill (DMD)
arch: all any
std-ver: 4.5.0
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 2.4.2-1+deb9u3
o-o-sec: 2.4.2-1+deb9u3
oldstable: 2.16.0-1
stable: 2.16.9-0.1
testing: 2.16.9-0.1
unstable: 2.16.9-0.1

versioned links

2.4.2-1+deb9u3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.16.0-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.16.9-0.1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

libmbedcrypto3
libmbedtls-dev (1 bugs: 0, 0, 1, 0)
libmbedtls-doc
libmbedtls12
libmbedx509-0

action needed

Debci reports failed tests high

unstable: pass (log)
The tests ran in 0:00:44
Last run: 2020-05-16T20:53:02.000Z
Previous status: pass

testing: pass (log)
The tests ran in 0:00:38
Last run: 2021-08-11T14:30:32.000Z
Previous status: pass

stable: fail (log)
The tests ran in 0:00:35
Last run: 2021-03-21T20:49:32.000Z
Previous status: None

Created: 2021-03-21 Last update: 2021-09-22 17:39

A new upstream version is available: 3.0.0 high

A new upstream version 3.0.0 is available, you should consider packaging it.

Created: 2020-06-29 Last update: 2021-09-22 14:36

The VCS repository is not up to date, push the missing commits. high

vcswatch reports that the current version of the package is not in its VCS.
Either you need to push your commits and/or your tags, or the information about the package's VCS are out of date. A common cause of the latter issue when using the Git VCS is not specifying the correct branch when the packaging is not in the default one (remote HEAD branch), which is usually "master" but can be modified in salsa.debian.org in the project's general settings with the "Default Branch" field). Alternatively the Vcs-Git field in debian/control can contain a "-b <branch-name>" suffix to indicate what branch is used for the Debian packaging.

Created: 2020-12-27 Last update: 2021-09-17 20:41

19 security issues in stretch high

There are 19 open security issues in stretch.

4 important issues:

CVE-2020-36475: An issue was discovered in Mbed TLS before 2.25.0 (and before 2.16.9 LTS and before 2.7.18 LTS). The calculations performed by mbedtls_mpi_exp_mod are not limited; thus, supplying overly large parameters could lead to denial of service when generating Diffie-Hellman key pairs.
CVE-2020-36476: An issue was discovered in Mbed TLS before 2.24.0 (and before 2.16.8 LTS and before 2.7.17 LTS). There is missing zeroization of plaintext buffers in mbedtls_ssl_read to erase unused application data from memory.
CVE-2020-36477: An issue was discovered in Mbed TLS before 2.24.0. The verification of X.509 certificates when matching the expected common name (the cn argument of mbedtls_x509_crt_verify) with the actual certificate name is mishandled: when the subjecAltName extension is present, the expected name is compared to any name in that extension regardless of its type. This means that an attacker could impersonate a 4-byte or 16-byte domain by getting a certificate for the corresponding IPv4 or IPv6 address (this would require the attacker to control that IP address, though).
CVE-2020-36478: An issue was discovered in Mbed TLS before 2.25.0 (and before 2.16.9 LTS and before 2.7.18 LTS). A NULL algorithm parameters entry looks identical to an array of REAL (size zero) and thus the certificate is considered valid. However, if the parameters do not match in any way, then the certificate should be considered invalid.

15 issues postponed or untriaged:

CVE-2018-19608: (needs triaging) Arm Mbed TLS before 2.14.1, before 2.7.8, and before 2.1.17 allows a local unprivileged attacker to recover the plaintext of RSA decryption, which is used in RSA-without-(EC)DH(E) cipher suites.
CVE-2018-9988: (needs triaging) ARM mbed TLS before 2.1.11, before 2.7.2, and before 2.8.0 has a buffer over-read in ssl_parse_server_key_exchange() that could cause a crash on invalid input.
CVE-2018-9989: (needs triaging) ARM mbed TLS before 2.1.11, before 2.7.2, and before 2.8.0 has a buffer over-read in ssl_parse_server_psk_hint() that could cause a crash on invalid input.
CVE-2019-16910: (needs triaging) Arm Mbed TLS before 2.19.0 and Arm Mbed Crypto before 2.0.0, when deterministic ECDSA is enabled, use an RNG with insufficient entropy for blinding, which might allow an attacker to recover a private key via side-channel attacks if a victim signs the same message many times. (For Mbed TLS, the fix is also available in versions 2.7.12 and 2.16.3.)
CVE-2019-18222: (needs triaging) The ECDSA signature implementation in ecdsa.c in Arm Mbed Crypto 2.1 and Mbed TLS through 2.19.1 does not reduce the blinded scalar before computing the inverse, which allows a local attacker to recover the private key via side-channel attacks.
CVE-2020-10932: (needs triaging) An issue was discovered in Arm Mbed TLS before 2.16.6 and 2.7.x before 2.7.15. An attacker that can get precise enough side-channel measurements can recover the long-term ECDSA private key by (1) reconstructing the projective coordinate of the result of scalar multiplication by exploiting side channels in the conversion to affine coordinates; (2) using an attack described by Naccache, Smart, and Stern in 2003 to recover a few bits of the ephemeral scalar from those projective coordinates via several measurements; and (3) using a lattice attack to get from there to the long-term ECDSA private key used for the signatures. Typically an attacker would have sufficient access when attacking an SGX enclave and controlling the untrusted OS.
CVE-2020-10941: (needs triaging) Arm Mbed TLS before 2.16.5 allows attackers to obtain sensitive information (an RSA private key) by measuring cache usage during an import.
CVE-2020-16150: (needs triaging) A Lucky 13 timing side channel in mbedtls_ssl_decrypt_buf in library/ssl_msg.c in Trusted Firmware Mbed TLS through 2.23.0 allows an attacker to recover secret key information. This affects CBC mode because of a computed time difference based on a padding length.
CVE-2020-36421: (needs triaging) An issue was discovered in Arm Mbed TLS before 2.23.0. Because of a side channel in modular exponentiation, an RSA private key used in a secure enclave could be disclosed.
CVE-2020-36422: (needs triaging) An issue was discovered in Arm Mbed TLS before 2.23.0. A side channel allows recovery of an ECC private key, related to mbedtls_ecp_check_pub_priv, mbedtls_pk_parse_key, mbedtls_pk_parse_keyfile, mbedtls_ecp_mul, and mbedtls_ecp_mul_restartable.
CVE-2020-36423: (needs triaging) An issue was discovered in Arm Mbed TLS before 2.23.0. A remote attacker can recover plaintext because a certain Lucky 13 countermeasure doesn't properly consider the case of a hardware accelerator.
CVE-2020-36424: (needs triaging) An issue was discovered in Arm Mbed TLS before 2.24.0. An attacker can recover a private key (for RSA or static Diffie-Hellman) via a side-channel attack against generation of base blinding/unblinding values.
CVE-2020-36425: (needs triaging) An issue was discovered in Arm Mbed TLS before 2.24.0. It incorrectly uses a revocationDate check when deciding whether to honor certificate revocation via a CRL. In some situations, an attacker can exploit this by changing the local clock.
CVE-2020-36426: (needs triaging) An issue was discovered in Arm Mbed TLS before 2.24.0. mbedtls_x509_crl_parse_der has a buffer over-read (of one byte).
CVE-2021-24119: (needs triaging) In Trusted Firmware Mbed TLS 2.24.0, a side-channel vulnerability in base64 PEM file decoding allows system-level (administrator) attackers to obtain information about secret RSA keys via a controlled-channel and side-channel attack on software running in isolated environments that can be single stepped, especially Intel SGX.

Created: 2021-08-23 Last update: 2021-08-24 05:07

2 security issues in sid high

There are 2 open security issues in sid.

2 important issues:

CVE-2020-36477: An issue was discovered in Mbed TLS before 2.24.0. The verification of X.509 certificates when matching the expected common name (the cn argument of mbedtls_x509_crt_verify) with the actual certificate name is mishandled: when the subjecAltName extension is present, the expected name is compared to any name in that extension regardless of its type. This means that an attacker could impersonate a 4-byte or 16-byte domain by getting a certificate for the corresponding IPv4 or IPv6 address (this would require the attacker to control that IP address, though).
CVE-2021-24119: In Trusted Firmware Mbed TLS 2.24.0, a side-channel vulnerability in base64 PEM file decoding allows system-level (administrator) attackers to obtain information about secret RSA keys via a controlled-channel and side-channel attack on software running in isolated environments that can be single stepped, especially Intel SGX.

Created: 2021-07-26 Last update: 2021-08-24 05:07

16 security issues in buster high

There are 16 open security issues in buster.

4 important issues:

CVE-2020-36475: An issue was discovered in Mbed TLS before 2.25.0 (and before 2.16.9 LTS and before 2.7.18 LTS). The calculations performed by mbedtls_mpi_exp_mod are not limited; thus, supplying overly large parameters could lead to denial of service when generating Diffie-Hellman key pairs.
CVE-2020-36476: An issue was discovered in Mbed TLS before 2.24.0 (and before 2.16.8 LTS and before 2.7.17 LTS). There is missing zeroization of plaintext buffers in mbedtls_ssl_read to erase unused application data from memory.
CVE-2020-36477: An issue was discovered in Mbed TLS before 2.24.0. The verification of X.509 certificates when matching the expected common name (the cn argument of mbedtls_x509_crt_verify) with the actual certificate name is mishandled: when the subjecAltName extension is present, the expected name is compared to any name in that extension regardless of its type. This means that an attacker could impersonate a 4-byte or 16-byte domain by getting a certificate for the corresponding IPv4 or IPv6 address (this would require the attacker to control that IP address, though).
CVE-2020-36478: An issue was discovered in Mbed TLS before 2.25.0 (and before 2.16.9 LTS and before 2.7.18 LTS). A NULL algorithm parameters entry looks identical to an array of REAL (size zero) and thus the certificate is considered valid. However, if the parameters do not match in any way, then the certificate should be considered invalid.

12 issues left for the package maintainer to handle:

CVE-2019-16910: (needs triaging) Arm Mbed TLS before 2.19.0 and Arm Mbed Crypto before 2.0.0, when deterministic ECDSA is enabled, use an RNG with insufficient entropy for blinding, which might allow an attacker to recover a private key via side-channel attacks if a victim signs the same message many times. (For Mbed TLS, the fix is also available in versions 2.7.12 and 2.16.3.)
CVE-2019-18222: (needs triaging) The ECDSA signature implementation in ecdsa.c in Arm Mbed Crypto 2.1 and Mbed TLS through 2.19.1 does not reduce the blinded scalar before computing the inverse, which allows a local attacker to recover the private key via side-channel attacks.
CVE-2020-10932: (needs triaging) An issue was discovered in Arm Mbed TLS before 2.16.6 and 2.7.x before 2.7.15. An attacker that can get precise enough side-channel measurements can recover the long-term ECDSA private key by (1) reconstructing the projective coordinate of the result of scalar multiplication by exploiting side channels in the conversion to affine coordinates; (2) using an attack described by Naccache, Smart, and Stern in 2003 to recover a few bits of the ephemeral scalar from those projective coordinates via several measurements; and (3) using a lattice attack to get from there to the long-term ECDSA private key used for the signatures. Typically an attacker would have sufficient access when attacking an SGX enclave and controlling the untrusted OS.
CVE-2020-10941: (needs triaging) Arm Mbed TLS before 2.16.5 allows attackers to obtain sensitive information (an RSA private key) by measuring cache usage during an import.
CVE-2020-16150: (needs triaging) A Lucky 13 timing side channel in mbedtls_ssl_decrypt_buf in library/ssl_msg.c in Trusted Firmware Mbed TLS through 2.23.0 allows an attacker to recover secret key information. This affects CBC mode because of a computed time difference based on a padding length.
CVE-2020-36421: (needs triaging) An issue was discovered in Arm Mbed TLS before 2.23.0. Because of a side channel in modular exponentiation, an RSA private key used in a secure enclave could be disclosed.
CVE-2020-36422: (needs triaging) An issue was discovered in Arm Mbed TLS before 2.23.0. A side channel allows recovery of an ECC private key, related to mbedtls_ecp_check_pub_priv, mbedtls_pk_parse_key, mbedtls_pk_parse_keyfile, mbedtls_ecp_mul, and mbedtls_ecp_mul_restartable.
CVE-2020-36423: (needs triaging) An issue was discovered in Arm Mbed TLS before 2.23.0. A remote attacker can recover plaintext because a certain Lucky 13 countermeasure doesn't properly consider the case of a hardware accelerator.
CVE-2020-36424: (needs triaging) An issue was discovered in Arm Mbed TLS before 2.24.0. An attacker can recover a private key (for RSA or static Diffie-Hellman) via a side-channel attack against generation of base blinding/unblinding values.
CVE-2020-36425: (needs triaging) An issue was discovered in Arm Mbed TLS before 2.24.0. It incorrectly uses a revocationDate check when deciding whether to honor certificate revocation via a CRL. In some situations, an attacker can exploit this by changing the local clock.
CVE-2020-36426: (needs triaging) An issue was discovered in Arm Mbed TLS before 2.24.0. mbedtls_x509_crl_parse_der has a buffer over-read (of one byte).
CVE-2021-24119: (needs triaging) In Trusted Firmware Mbed TLS 2.24.0, a side-channel vulnerability in base64 PEM file decoding allows system-level (administrator) attackers to obtain information about secret RSA keys via a controlled-channel and side-channel attack on software running in isolated environments that can be single stepped, especially Intel SGX.

You can find information about how to handle these issues in the security team's documentation.

Created: 2021-02-19 Last update: 2021-08-24 05:07

2 security issues in bullseye high

There are 2 open security issues in bullseye.

1 important issue:

CVE-2020-36477: An issue was discovered in Mbed TLS before 2.24.0. The verification of X.509 certificates when matching the expected common name (the cn argument of mbedtls_x509_crt_verify) with the actual certificate name is mishandled: when the subjecAltName extension is present, the expected name is compared to any name in that extension regardless of its type. This means that an attacker could impersonate a 4-byte or 16-byte domain by getting a certificate for the corresponding IPv4 or IPv6 address (this would require the attacker to control that IP address, though).

1 issue left for the package maintainer to handle:

CVE-2021-24119: (needs triaging) In Trusted Firmware Mbed TLS 2.24.0, a side-channel vulnerability in base64 PEM file decoding allows system-level (administrator) attackers to obtain information about secret RSA keys via a controlled-channel and side-channel attack on software running in isolated environments that can be single stepped, especially Intel SGX.

You can find information about how to handle this issue in the security team's documentation.

Created: 2021-08-14 Last update: 2021-08-24 05:07

2 security issues in bookworm high

There are 2 open security issues in bookworm.

2 important issues:

CVE-2020-36477: An issue was discovered in Mbed TLS before 2.24.0. The verification of X.509 certificates when matching the expected common name (the cn argument of mbedtls_x509_crt_verify) with the actual certificate name is mishandled: when the subjecAltName extension is present, the expected name is compared to any name in that extension regardless of its type. This means that an attacker could impersonate a 4-byte or 16-byte domain by getting a certificate for the corresponding IPv4 or IPv6 address (this would require the attacker to control that IP address, though).
CVE-2021-24119: In Trusted Firmware Mbed TLS 2.24.0, a side-channel vulnerability in base64 PEM file decoding allows system-level (administrator) attackers to obtain information about secret RSA keys via a controlled-channel and side-channel attack on software running in isolated environments that can be single stepped, especially Intel SGX.

Created: 2021-08-15 Last update: 2021-08-24 05:07

2 bugs tagged patch in the BTS normal

The BTS contains patches fixing 2 bugs, consider including or untagging them.

Created: 2021-08-14 Last update: 2021-09-22 17:31

Build log checks report 1 warning low

Build log checks report 1 warning

Created: 2018-12-08 Last update: 2018-12-08 07:43

Standards version of the package is outdated. wishlist

The package should be updated to follow the last version of Debian Policy (Standards-Version 4.6.0 instead of 4.5.0).

Created: 2020-11-17 Last update: 2021-08-18 14:03

news

[rss feed]

[2020-12-29] mbedtls 2.16.9-0.1 MIGRATED to testing (Debian testing watch)
[2020-12-27] Accepted mbedtls 2.16.9-0.1 (source) into unstable (Wookey)
[2020-03-03] mbedtls 2.16.5-1 MIGRATED to testing (Debian testing watch)
[2020-02-29] Accepted mbedtls 2.16.5-1 (source) into unstable (James Cowgill)
[2020-01-31] mbedtls 2.16.4-1 MIGRATED to testing (Debian testing watch)
[2020-01-28] Accepted mbedtls 2.16.4-1 (source) into unstable (James Cowgill)
[2019-10-01] mbedtls 2.16.3-1 MIGRATED to testing (Debian testing watch)
[2019-09-28] Accepted mbedtls 2.16.3-1 (source) into unstable (James Cowgill)
[2019-07-18] mbedtls 2.16.2-1 MIGRATED to testing (Debian testing watch)
[2019-07-15] Accepted mbedtls 2.16.2-1 (source) into unstable (James Cowgill)
[2019-01-10] mbedtls 2.16.0-1 MIGRATED to testing (Debian testing watch)
[2019-01-08] Accepted mbedtls 2.16.0-1 (source) into unstable (James Cowgill)
[2018-12-17] mbedtls 2.14.1-2 MIGRATED to testing (Debian testing watch)
[2018-12-07] Accepted mbedtls 2.14.1-2 (source) into unstable (James Cowgill)
[2018-12-07] Accepted mbedtls 2.14.1-1 (source) into unstable (James Cowgill)
[2018-10-09] mbedtls 2.13.0-3 MIGRATED to testing (Debian testing watch)
[2018-10-04] Accepted mbedtls 2.13.0-3 (source) into unstable (James Cowgill)
[2018-10-02] Accepted mbedtls 2.4.2-1+deb9u3 (source) into proposed-updates->stable-new, proposed-updates (James Cowgill)
[2018-10-01] Accepted mbedtls 2.13.0-2 (source) into experimental (James Cowgill)
[2018-09-24] Accepted mbedtls 2.13.0-1 (all amd64 source) into experimental, experimental (James Cowgill)
[2018-09-16] Accepted mbedtls 2.4.2-1+deb9u3 (source) into stable->embargoed, stable (James Cowgill)
[2018-07-31] mbedtls 2.12.0-1 MIGRATED to testing (Debian testing watch)
[2018-07-28] Accepted mbedtls 2.12.0-1 (source) into unstable (James Cowgill)
[2018-07-13] mbedtls 2.11.0-1 MIGRATED to testing (Debian testing watch)
[2018-07-10] Accepted mbedtls 2.11.0-1 (source) into unstable (James Cowgill)
[2018-05-30] mbedtls 2.9.0-2 MIGRATED to testing (Debian testing watch)
[2018-05-27] Accepted mbedtls 2.9.0-2 (source) into unstable (James Cowgill)
[2018-05-10] Accepted mbedtls 2.9.0-1 (source amd64 all) into experimental, experimental (James Cowgill)
[2018-04-15] mbedtls 2.8.0-1 MIGRATED to testing (Debian testing watch)
[2018-04-09] Accepted mbedtls 2.8.0-1 (source) into unstable (James Cowgill)

bugs [bug history graph]

all: 5
RC: 0
I&N: 2
M&W: 3
F&P: 0
patch: 2

links

homepage
lintian
buildd: logs, checks, clang, reproducibility, cross
popcon
browse source code
edit tags
other distros
security tracker
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 2.16.9-0.1ubuntu1
patches for 2.16.9-0.1ubuntu1