Passing an attacker controlled size when creating an IOBuf could cause integer overflow, leading to an out of bounds write on the heap with the possibility of remote code…

Improper handling of close_notify alerts can result in an out-of-bounds read in AsyncSSLSocket

folly::secureRandom will re-use a buffer between parent and child processes when fork() is called