HHVM 4.172.0 and all prior versions use TLS 1.0 for secure connections when handling tls:// URLs in the stream extension

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…

When unserializing an object with dynamic properties HHVM needs to pre-reserve the full size of the dynamic property array before inserting anything into it

Due to incorrect string size calculations inside the preg_quote function, a large input string passed to the function can trigger an integer overflow leading to a heap overflow

xbuf_format_converter, used as part of exif_read_data, was appending a terminating null character to the generated string, but was not using its standard append char function

An incorrect size calculation in ldap_escape may lead to an integer overflow when overly long input is passed in, resulting in an out-of-bounds write

mcrypt_get_block_size did not enforce that the provided "module" parameter was a string, leading to type confusion if other types of data were passed in

Insufficient type checks were employed prior to casting input data in SimpleXMLElement_exportNode and simplexml_import_dom

Various APC functions accept keys containing null bytes as input, leading to premature truncation of input

Insufficient boundary checks when processing a string in mb_ereg_replace allows access to out-of-bounds memory

An invalid free in mb_detect_order can cause the application to crash or potentially result in remote code execution

hhvm before 3.12.11 has a use-after-free in the serialize_memoize_param() and ResourceBundle::__construct() functions

Insufficient boundary checks when formatting numbers in number_format allows read/write access to out-of-bounds memory, potentially leading to remote code execution

Insufficient boundary checks when processing M_SOFx markers from JPEG headers in the GD extension could allow access to out-of-bounds memory via a maliciously constructed invalid…

Insufficient boundary checks when processing the JPEG APP12 block marker in the GD extension could allow access to out-of-bounds memory via a maliciously constructed invalid JPEG…

Insufficient boundary checks for the strrpos and strripos functions allow access to out-of-bounds memory

The implementations of streams for bz2 and php://output improperly implemented their readImpl functions, returning -1 consistently

The function number_format is vulnerable to a heap overflow issue when its second argument ($dec_points) is excessively large

Multipart-file uploads call variables to be improperly registered in the global scope

Infinite recursion in wddx in Facebook HHVM before 3.15.0 allows attackers to have unspecified impact via unknown vectors

The array_*_recursive functions in Facebook HHVM before 3.15.0 allows attackers to have unspecified impact via unknown vectors, related to recursion

Self recursion in compact in Facebook HHVM before 3.15.0 allows attackers to have unspecified impact via unknown vectors

Integer overflow in StringUtil::implode in Facebook HHVM before 3.15.0 allows attackers to have unspecified impact via unknown vectors

Integer overflow in bcmath in Facebook HHVM before 3.15.0 allows attackers to have unspecified impact via unknown vectors, which triggers a buffer overflow

Out-of-bounds write in the (1) mb_detect_encoding, (2) mb_send_mail, and (3) mb_detect_order functions in Facebook HHVM before 3.15.0 allows attackers to have unspecified impact…

HHVM supports the use of an "admin" server which accepts administrative requests over HTTP

Insufficient boundary checks when decoding JSON in JSON_parser allows read access to out of bounds memory, potentially leading to information leak and DOS

The Memcache::getextendedstats function can be used to trigger an out-of-bounds read

The unserialize() function supported a type code, "S", which was meant to be supported only for APC serialization

The fb_unserialize function did not impose a depth limit for nested deserialization

In the crypt function, we attempt to null terminate a buffer using the size of the input salt without validating that the offset is within the buffer

Incorrect bounds calculations in substr_compare could lead to an out-of-bounds read when the second string argument passed in is longer than the first

In-memory file operations (ie: using fopen on a data URI) did not properly restrict negative seeking, allowing for the reading of memory prior to the in-memory buffer

Insufficient boundary checks when decoding JSON in TryParse reads out of bounds memory, potentially leading to DOS

Insufficient boundary checks when decoding JSON in handleBackslash reads out of bounds memory, potentially leading to DOS

HHVM, when used with FastCGI, would bind by default to all available interfaces

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

A Malformed h2 frame can cause 'std::out_of_range' exception when parsing priority meta data

A potential denial-of-service issue in the Proxygen handling of invalid HTTP2 settings which can cause the server to spend disproportionate resources

HHVM does not attempt to address RFC 3875 section 4.1.18 namespace conflicts and therefore does not protect CGI applications from the presence of untrusted client data in the…