Vulnerability Note

[bperrin2]

Hi,

The following vulnerability described as Bluetooth implementations may not sufficiently validate elliptic curve parameters during Diffie-Hellman key exchange in the following page was recently published:

https://www.kb.cert.org/vuls/id/304725

Is the softdevice / nRF52840 concerned by a such vulnerability.

Thank you for having your opinion.

Bernard

[Jim Dattolo]

I came here to ask the same thing, can someone from Nordic chime in with a list of SD versions that have been checked for this vulnerability?  I'm currently on SDK14 SD 5.1.0 on a NRF52832 chip.

[Einar Thorsrud]

Hi,

We just published a white paper which describe this issue in detail: nWP031 - Security Threat in Bluetooth LESC Pairing.

In a nutshell, the problem is that the Bluetooth specification did not require that the remote public key be validated before it is used to calculate the shared secret during the Diffie–Hellman key exchange. The LE Secure Connection implementation for Nordic devices reside in SDK "space" rather than in the SoftDevice (stack), so this issue can be fixed in the SDK. The fix is to always validate the remote public key before it is used to generate the shared secret. This issue is not present in SDK 15.0.0, which always validates the remote public in the BLE LESC module.

[Bob J]

Hi

I was wondering how this affects BLE Mesh. If I was using SDK 14 but using NFC to transfer the DHEC parameters, would there still be a vulnerability? Or would the vulnerability only exist if I was not using NFC.

I read the white paper and it did not appear to address this question.

Thanks in advance for responding.

[Einar Thorsrud]

Hi,

BLE Mesh is not affected in any way. This issue only concerns LE Secure Connections (LESC) which is not used in BLE Mesh.