3 ms·
So, where does this come in: http://www.securityweek.com/high-severity-vulnerability-found-polarssl-library http://www.securityweek.com/high-severity-vulnerabil
by bsder 9y ago
So, where does this come in:
http://www.securityweek.com/high-severity-vulnerability-found-polarssl-library http://www.securityweek.com/high-severity-vulnerability-foun...
- sanxiyn 9y agoEasy, it was out of scope. Quoting the report, "This report states the immunity of the PolarSSL software component to widespread CWEs, provided that PolarSSL is deployed in a context where... The server is configured as to never ask for client-side certificates". Quoting the news, "Servers that don't ask for client certificates are not impacted". TrustInSoft could prove that part of code too. There's nothing special about it. It's just that they didn't bother.
- huhtenberg 9y agoIt doesn't. It's not a buffer overflow issue.
- sanxiyn 9y agoIt's an uninitialized read, and PolarSSL is actually also proven to lack uninitialized reads. It's just that asn1_get_sequence_of was not included in verification (as it is unreachable in verified configuration).
- unscaled 9y agoWhich shows you the limit of verification toolsets vs. a verifying compiler. To verify that the code is 100% free of uninitialized reads or uses-after-free the static analyzer would have to scan through all possible permutations. Sure, you can get very close to 100% in practice, but even if you're fine with this level of guarantee, the amount of discipline and cognitive overhead required for doing that in C makes Rust's learning seem like a piece of cake.