Skip Navigation
Majority of Critical Open Source Projects Contain Memory Unsafe Code
  • Not sure if that is even the point. The article is all about memory unsafe programming!!1!. But there is no context at all.

    Sure, there are vulnerabilities because of unsafe memory handling. But I looked for some statistic which would bring unsafe memory handling into context with say the high profile vulnerabilities from the last few weeks / months. I haven't spent too much time on research but looking at some lists containing vulns from the last few months it seems as if all those pre-auth, priv escalation, directory traversal and whatnot very based on much simpler failures like wrong error handling or logical errors or missing code than unsafe memory handling.

    I might be wrong, then please show me the numbers, but shooting at C/C++ because unsafe!!1! sounds like a very biased story there.

    And while we are at it. I'd also be interested in C vs. (somewhat modern) C++.

  • Google Paid 6 Billion to Be Default Search Engine in 2021
    www.bloomberg.com Google Paid $26 Billion to Be Default Search Engine in 2021

    Google paid $26.3 billion to other companies to ensure its search engine was the default on web browsers and mobile phones, a top company executive testified during the Justice Department’s antitrust trial Friday.

    Google Paid $26 Billion to Be Default Search Engine in 2021

    cross-posted from: https://infosec.pub/post/4231412

    > Google Paid 6 Billion to Be Default Search Engine in 2021

    0
    InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)KR
    krogoth @infosec.pub
    Posts 1
    Comments 4
    Moderates