When unserializing an object with dynamic properties HHVM needs to pre-reserve the full size of the dynamic property array before inserting
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. Otherwise the array might resize, invalidating previously stored references. This pre-reservation was not occurring in 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.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for help- Published
- Mar 10, 2021
- Updated
- Jun 16, 2026
- EPSS
- 1.4% · 71th percentile
- CWE
- CWE-416
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
39
Monitor
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.4%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| hhvm | cpe:2.3:a:facebook:hhvm |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- facebook hhvmbefore 4.32.3
- facebook hhvm4.33.0 and later · before 4.56.1
- facebook hhvm4.57.0
- facebook hhvm4.58.0
- facebook hhvm4.58.1
- facebook hhvm4.59.0
- facebook hhvm4.60.0
- facebook hhvm4.61.0
- facebook hhvm4.62.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (facebook). Independent of NVD's CPE analysis and usually ahead of it.
Facebook HHVM
- 4.62.0, 4.61.0, 4.60.0, 4.59.0, 4.57.0affected
- 4.62.1 and later · before unspecifiednot affected
- 4.61.1 and later · before unspecifiednot affected
- 4.60.1 and later · before unspecifiednot affected
- 4.59.1 and later · before unspecifiednot affected
- 4.58.2 and later · before unspecifiednot affected
- 4.58.0 and later · before unspecifiedaffected
- 4.57.1 and later · before unspecifiednot affected
- 4.56.1 and later · before unspecifiednot affected
- 4.33.0 and later · before unspecifiedaffected
Same product
facebook: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-11930An invalid free in mb_detect_order can cause the application to crash or potentially result in remote code execution.40Plan
- CVE-2019-11929Insufficient boundary checks when formatting numbers in number_format allows read/write access to out-of-bounds memory, potentially leading 40Plan
- CVE-2019-11926Insufficient boundary checks when processing M_SOFx markers from JPEG headers in the GD extension could allow access to out-of-bounds memory40Plan
- CVE-2019-11925Insufficient boundary checks when processing the JPEG APP12 block marker in the GD extension could allow access to out-of-bounds memory via 40Plan
- CVE-2019-3561Insufficient boundary checks for the strrpos and strripos functions allow access to out-of-bounds memory.40Plan
- CVE-2019-3557The implementations of streams for bz2 and php://output improperly implemented their readImpl functions, returning -1 consistently.40Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);Fixed
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
- github.com/facebook/hhvm/commit/c1c4bb0cf9e076aafaf4ff3515556ef9faf906f3
- hhvm.com/blog/2020/06/30/security-update.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.