Re:About the security content of iOS 7.0.6
by WaltSellers on Wednesday February 26, 2014 @10:55PM
(#7310313)
From a different point of view, part of the problem is the undefined state of the code at the "fail" label.
Execution will arrive there somehow, but the 'how' is unclear. The word "fail" implies you should reach that point only if there was an error, but that is a bad assumption in this case.
If the real answer to 'how did we get here?' was checked, then the bug could not hide in the undefined behavior. This would not allow a dangling goto to result in a false positive. A false negative will get someone's attention when their web page doesn't load.
Something like this could remove the undefined state:
goto pass;
fail:
if ( err == 0 ) {
assert( err != 0 ); // BUG! variable must contain an error number
err = kSomeAppropriateErrorNumber;
}
pass:
SSLFreeBuffer(&signedHashes);
SSLFreeBuffer(&hashCtx);
return err;
Re:About the security content of iOS 7.0.6
by kplaxmaster on Monday February 24, 2014 @01:37AM
(#7289405)
Haha love the whitespace comment. This also makes you think of the static source-code analysis done at Apple. Surely static tools would have picked this up, no...?
Re:About the security content of iOS 7.0.6
by subdigital on Monday February 24, 2014 @03:28PM
(#7293230)
Clang currently does not warn about this, but I'd wager that Xcode will boast a feature in the next version that detects dead code due to early returns/gotos.
Re:About the security content of iOS 7.0.6
by peternlewis on Monday February 24, 2014 @09:24PM
(#7294880)
Clang may not warn about white space issues, but it certainly does warn about unreachable code if -Wunreachable is on. This code would not compile in my project because the unconditional goto leaves the following code unreachable.
Re:About the security content of iOS 7.0.6
by WaltSellers on Wednesday February 26, 2014 @10:27PM
(#7310179)
Even if there were braces, the bug would still exist if the extra goto was outside the braces.
It might be more noticeable, but then, the original bug existed because no one noticed.
Others might say it's a problem of whitespace insensitive languages ;)