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. This issue affects HHVM versions prior to 4.56.3, all versions between 4.57.0 and 4.80.1, all versions between 4.81.0 and 4.93.1, and versions 4.94.0, 4.95.0, 4.96.0, 4.97.0, 4.98.0.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NFacebook Hhvm
APPFacebook4.94.04.95.04.96.04.97.04.98.04.81.0 – 4.93.2 (bez)4.57.0 – 4.80.2 (bez)< 4.56.3
Related vulnerabilities
HHVM 4.172.0 and all prior versions use TLS 1.0 for secure connections when handling tls:// URLs in the stream...
Passing an attacker controlled size when creating an IOBuf could cause integer overflow, leading to an out of ...
When unserializing an object with dynamic properties HHVM needs to pre-reserve the full size of the dynamic pr...
Due to incorrect string size calculations inside the preg_quote function, a large input string passed to the f...
An incorrect size calculation in ldap_escape may lead to an integer overflow when overly long input is passed ...