> It is worth noting that this change could potentially leave implementations vulnerable to Bleichenbacher’s attack on PKCS#1 v1.5 RSA padding. In our implementation, these concerns are not an issue as there we have no access to any of the decrypt responses or stack traces.
You don't need those things to exploit a padding oracle. A timing leak is sufficient.
Unless you're doing what s2n does to blind response times of any potential timing leaks, you're probably still vulnerable.
You don't need those things to exploit a padding oracle. A timing leak is sufficient.
Unless you're doing what s2n does to blind response times of any potential timing leaks, you're probably still vulnerable.
https://github.com/aws/s2n-tls#timing-blinding
You're probably not using s2n to talk to a Nitro enclave.