CVE-2016-1000006
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedhhvm before 3.12.11 has a use-after-free in the serialize_memoize_param() and ResourceBundle::__construct() functions.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceUse-after-free vulnerability in HHVM (HipHop Virtual Machine) affecting serialize_memoize_param() and ResourceBundle::__construct() functions. This memory corruption issue allows arbitrary code execution and is rated critical due to the high impact of memory safety vulnerabilities.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 3.12.11CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify HHVM is installedRun `which hhvm` or `hhvm --version` to confirm HHVM is present on the systemAffected if HHVM command is found and returns a version number
-
Determine installed HHVM versionExecute `hhvm --version` and extract the full version string (e.g., 3.10.0, 3.12.5, etc.)Affected if Version output is returned showing a version number less than 3.12.11
-
Compare version against affected rangeParse the version number from step 2 and compare it to the affected range: any version < 3.12.11 is vulnerableAffected if Installed version is 3.12.10 or lower, or any 3.x version below 3.12.11
-
Identify if vulnerable functions are in use (optional)Search application code for calls to `serialize_memoize_param()` or instantiation of `ResourceBundle` class via `new ResourceBundle()`Affected if Code uses either function and HHVM version is in the affected range
A system is affected if HHVM is installed and the running version is any version lower than 3.12.11, particularly if code utilizes the serialize_memoize_param() or ResourceBundle::__construct() functions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.12.11
Upgrade to HHVM version 3.12.11 or later to patch the use-after-free vulnerability. If immediate upgrade is not feasible, restrict network exposure and monitor for exploitation attempts.
HHVM 3.12.11 or later
- Identify the current HHVM version installed in the environment
- Plan downtime window for the upgrade process
- Back up any critical data and configuration files
- Upgrade HHVM to version 3.12.11 or later
- Verify the upgrade was successful by checking the new HHVM version
- Restart any services or applications that depend on HHVM
- Test that affected functionality (serialize_memoize_param and ResourceBundle) works correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-1000006 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-1000006 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data