Skip to content
Sign in
Not rated

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

Description

The unserialize() function supported a type code, "S", which was meant to be supported only for APC serialization. This type code allowed arbitrary memory addresses to be accessed as if they were static StringData objects. This issue affected HHVM prior to v4.32.3, between versions 4.33.0 and 4.56.0, 4.57.0, 4.58.0, 4.58.1, 4.59.0, 4.60.0, 4.61.0, 4.62.0.

Affected products and versions

Product Affected versions Fixed in
HHVM 4.62.0 4.62.1
HHVM 4.61.0 4.61.1
HHVM 4.60.0 4.60.1
HHVM 4.59.0 4.59.1
HHVM 4.58 4.58.0 → < 4.58.2 4.58.2
HHVM 4.57.0 4.57.1
HHVM 4.56 earliest → < 4.56.1 4.56.1
HHVM 4.33 4.33.0 → latest No fix stated
HHVM 4.32 earliest → < 4.32.3 4.32.3

Other CVEs of HHVM

The 31 CVEs of HHVM →
CVE-2022-36937 HHVM 4.172.0 and all prior versions use TLS 1.0 for secure connections when handling tls:// URLs in the stream extension 9.8 Critical CVE-2019-3556 HHVM supports the use of an "admin" server which accepts administrative requests over HTTP Not rated CVE-2021-24036 Passing an attacker controlled size when creating an IOBuf could cause integer overflow, leading to an out of bounds… Not rated CVE-2020-1900 When unserializing an object with dynamic properties HHVM needs to pre-reserve the full size of the dynamic property… Not rated
Track this CVE