4 ms·

Here's Mozilla Firefox, search for "use-after-free", "memory safety hazard". https://www.mozilla.org/en-US/security/known-vulnerabilities/firefox/ https://www.

Here's Mozilla Firefox, search for "use-after-free", "memory safety hazard". https://www.mozilla.org/en-US/security/known-vulnerabilities/firefox/ https://www.mozilla.org/en-US/security/known-vulnerabilities... Here's Google Chrome, search for "buffer overflow", "Use after free", "out-of-bounds": http://googlechromereleases.blogspot.com/search/label/Stable%20updates http://googlechromereleases.blogspot.com/search/label/Stable... Edit: Chromium bug tracker talks to me now, query for "use-after-free" has 2157 results: https://bugs.chromium.org/p/chromium/issues/list?can=1&q=type%3Dbug-security+use-after-free&colspec=ID+Pri+M+Stars+ReleaseBlock+Component+Status+Owner+Summary+OS+Modified&x=m&y=releaseblock&cells=ids https://bugs.chromium.org/p/chromium/issues/list?can=1&q=typ...

lossolo 10y ago
Once again, show me ONLY modern c++ code base. Those are mixed with old C++ code base. Still waiting. And read how chromium use C++11... (https://chromium-cpp.appspot.com/ https://chromium-cpp.appspot.com/) + google style guide that is prehistory and NOT considered good in community. Maybe try with proxygen, rocksdb, folly from facebook ?
- pcwalton 10y ago
  > Once again, show me ONLY modern c++ code base. Those are mixed with old C++ code base. These security flaws are in code that has used smart pointers for years and years. > And read how chromium use C++11... (https://chromium-cpp.appspot.com/ https://chromium-cpp.appspot.com/) + google style guide that is prehistory and NOT considered good in community. It doesn't matter from a security perspective. In fact, I think C++11 is actually less safe than C++03 with custom smart pointers, because use-after-move is a hazard and lambdas make it very easy to have dangling references. Chromium security engineers are some of the most competent engineers in their field. If using more C++11 features made their code more secure, they would do so. They don't, because C++11 doesn't make their code more secure. Ultimately, these debates are really premised on something absurd: "assume modern C++ is completely memory safe unless proved otherwise". This is completely backwards and leads to endless "no true Scotsman" games. You need to show why C++ is supposedly memory safe. You won't be able to, because C++ is not. > Maybe try with proxygen, rocksdb, folly from facebook ? Those codebases aren't being attacked the same way browsers are. But I can easily find use-after-free in them too with Google: http://code.metager.de/source/history/facebook/folly/folly/io/async/test/DelayedDestructionBaseTest.cpp http://code.metager.de/source/history/facebook/folly/folly/i...
  - lossolo 10y ago
    Indeed you have found ONE, Good job.. I didn't say modern c++ is memory safe, did I? I've said couple of times that someone can use modern c++ with good static analyzer in safe way if his application is properly designed. Tell me then if it's such a huge problem that rust solves ( that people have with memory safety) why whole world didn't switched to Rust for NEW projects? It's stable already.

lossolo 10y ago

Once again, show me ONLY modern c++ code base. Those are mixed with old C++ code base. Still waiting. And read how chromium use C++11... (https://chromium-cpp.appspot.com/ https://chromium-cpp.appspot.com/) + google style guide that is prehistory and NOT considered good in community. Maybe try with proxygen, rocksdb, folly from facebook ?

pcwalton 10y ago
> Once again, show me ONLY modern c++ code base. Those are mixed with old C++ code base. These security flaws are in code that has used smart pointers for years and years. > And read how chromium use C++11... (https://chromium-cpp.appspot.com/ https://chromium-cpp.appspot.com/) + google style guide that is prehistory and NOT considered good in community. It doesn't matter from a security perspective. In fact, I think C++11 is actually less safe than C++03 with custom smart pointers, because use-after-move is a hazard and lambdas make it very easy to have dangling references. Chromium security engineers are some of the most competent engineers in their field. If using more C++11 features made their code more secure, they would do so. They don't, because C++11 doesn't make their code more secure. Ultimately, these debates are really premised on something absurd: "assume modern C++ is completely memory safe unless proved otherwise". This is completely backwards and leads to endless "no true Scotsman" games. You need to show why C++ is supposedly memory safe. You won't be able to, because C++ is not. > Maybe try with proxygen, rocksdb, folly from facebook ? Those codebases aren't being attacked the same way browsers are. But I can easily find use-after-free in them too with Google: http://code.metager.de/source/history/facebook/folly/folly/io/async/test/DelayedDestructionBaseTest.cpp http://code.metager.de/source/history/facebook/folly/folly/i...
- lossolo 10y ago
  Indeed you have found ONE, Good job.. I didn't say modern c++ is memory safe, did I? I've said couple of times that someone can use modern c++ with good static analyzer in safe way if his application is properly designed. Tell me then if it's such a huge problem that rust solves ( that people have with memory safety) why whole world didn't switched to Rust for NEW projects? It's stable already.