Security readout for executives and security teams
Plain-English summary
This is an old HHVM XML-handling flaw caused by weak type checks before data casting. The provided sources identify affected HHVM version ranges but do not provide CVSS severity, impact details, or evidence of active exploitation.
Executive priority
Prioritize if HHVM remains in use, particularly on internet-facing or XML-processing services. If HHVM is absent, business urgency is low but should be documented as not applicable.
Technical view
HHVM performed insufficient type checks before casting input data in SimpleXMLElement_exportNode and simplexml_import_dom. Affected ranges are before 3.9.5, 3.10.0 through 3.12.3, and 3.13.0 through 3.14.1 inclusive.
Likely exposure
Exposure is likely limited to systems still running the affected HHVM versions, especially applications that process XML or DOM data. The bundle does not identify affected downstream products.
Exploitation context
The source bundle does not cite public exploitation, KEV inclusion, exploit availability, or real-world attacks. Treat exploitation status as unconfirmed based on the provided evidence.
Researcher notes
The bundle is specific about affected HHVM versions and vulnerable functions, but sparse on impact mechanics, CVSS, CWE, exploitability, and confirmed fixes. Avoid assuming more than version-based exposure without vendor advisory review.
Mitigation direction
- Inventory all HHVM runtimes and record exact versions.
- Upgrade HHVM systems out of the affected version ranges.
- Review Facebook or HHVM advisory guidance before selecting remediation.
- Reduce exposure of XML or DOM processing paths handling untrusted input.
Validation and detection
- Confirm whether production or build systems run HHVM.
- Compare discovered HHVM versions against the affected ranges.
- Identify application paths using SimpleXML or DOM import behavior.
- Check vendor advisory and commit references for remediation confirmation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2016-1000004 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/facebook/hhvm/commit/8e7266fef1f329b805b37f32c9ad0090215ab269CVE reference · x_refsource_CONFIRM
- https://www.facebook.com/security/advisories/cve-2016-1000004CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.