Re:CVE-2022-0329 and the problems with automated vulnerabili...
by phendrenad2 on Saturday January 29, 2022 @01:57PM
(#30129228)
Part of the problem is, vulnerability scans are the only tool for vulnerability management that our puny tiny pathetic programmer brains have invented. Now, realistically, it would make a lot more sense if libraries that call pickle() had some kind of "use warning" attached to them, which your IDE would use to detect when you do something that opens you up to compromise (such as using untrusted user data in some weird contrived context that forces a library to call pickle() on it). But NO. You CANNOT have this. Everything MUST be a CVE.
[ Parent
| on HN ]
Re:CVE-2022-0329 and the problems with automated vulnerabili...
by orf on Saturday January 29, 2022 @02:15PM
(#30129423)
This is quite hard to do correctly though? I think you're talking about tainting all user inputs and tracing their path through a system, but this is non trivial and quite possibly impossible in the general case.