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.
{
"binaries": [
{
"binary_name": "libmbedcrypto0",
"binary_version": "2.2.1-2ubuntu0.3"
},
{
"binary_name": "libmbedtls-dev",
"binary_version": "2.2.1-2ubuntu0.3"
},
{
"binary_name": "libmbedtls10",
"binary_version": "2.2.1-2ubuntu0.3"
},
{
"binary_name": "libmbedx509-0",
"binary_version": "2.2.1-2ubuntu0.3"
}
]
}
{
"binaries": [
{
"binary_name": "libmbedcrypto1",
"binary_version": "2.8.0-1ubuntu0.1~esm1"
},
{
"binary_name": "libmbedtls-dev",
"binary_version": "2.8.0-1ubuntu0.1~esm1"
},
{
"binary_name": "libmbedtls10",
"binary_version": "2.8.0-1ubuntu0.1~esm1"
},
{
"binary_name": "libmbedx509-0",
"binary_version": "2.8.0-1ubuntu0.1~esm1"
}
]
}
{
"binaries": [
{
"binary_name": "libmbedcrypto3",
"binary_version": "2.16.4-1ubuntu2+esm1"
},
{
"binary_name": "libmbedtls-dev",
"binary_version": "2.16.4-1ubuntu2+esm1"
},
{
"binary_name": "libmbedtls12",
"binary_version": "2.16.4-1ubuntu2+esm1"
},
{
"binary_name": "libmbedx509-0",
"binary_version": "2.16.4-1ubuntu2+esm1"
}
]
}