Re:Report on the technical vulnerabilities found in Huawei 5...
by mikeash on Friday July 12, 2019 @03:54PM
(#20423885)
I don’t understand. Your link is talking about the difficulty of using these functions. But here, the functions are already being used. What’s missing is implementations of them. They chose to implement these functions without the security checks, but implementing them with the security checks is not hard.
[ Parent
| on HN ]
Re:Report on the technical vulnerabilities found in Huawei 5...
by userbinator on Friday July 12, 2019 @10:07PM
(#20426083)
That whole article is basically saying that those extra checks are useless anyway in correctly written code, as otherwise it would be code that can be tested and reached:
On the other hand, in code that does check for and attempts to handle errors reported by the APIs, the new error handling paths tend to be poorly tested (if at all) because the runtime-constraint violation can typically be triggered only once, the first time it is found and before it's fixed. After the flaw is removed, the handling code can no longer be tested and, as the code evolves, can become a source of defects in the program.
Re:Report on the technical vulnerabilities found in Huawei 5...
by microtherion on Friday July 12, 2019 @10:08PM
(#20426086)
It's possible that they are calling the functions, but passing incorrect length arguments so frequently that they are best ignored.