The fb_unserialize function did not impose a depth limit for nested deserialization
Facebook HHVM
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Facebook HHVM |
|
|
Facebook HHVM
| Product | Affected | Fixed in |
|---|---|---|
| Facebook HHVM |
|
|
The fb_unserialize function did not impose a depth limit for nested deserialization. That meant a maliciously constructed string could cause deserialization to recurse, leading to stack exhaustion. 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.
From the CVE record · facebook
HHVM's fb_unserialize function lacks a depth limit for nested deserialization. A maliciously constructed string passed to the function can cause recursion and exhaust the stack. The input does not specify network access, authentication requirements, or user interaction.
Engineers running HHVM prior to v4.32.3, from v4.33.0 through v4.56.0, or v4.57.0, v4.58.0, v4.58.1, v4.59.0, v4.60.0, v4.61.0, or v4.62.0 should check their deployments.