CVE intelligence and bounded remediation

CVE-2019-3570 — Call to the scrypt_enc() function in HHVM can lead to heap corruption by using specifically crafted parameters (N, r and p)

Critical CVSS 9.8

Call to the scrypt_enc() function in HHVM can lead to heap corruption by using specifically crafted parameters (N, r and p). This happens if the parameters are configurable by an attacker for instance by providing the output of scrypt_enc() in a context where Hack/PHP code would attempt to verify it by re-running scrypt_enc() with the same parameters. This could result in information disclosure, memory being overwriten or crashes of the HHVM process. This issue affects versions 4.3.0, 4.4.0, 4.5.0, 4.6.0, 4.7.0, 4.8.0, versions 3.30.5 and below, and all versions in the 4.0, 4.1, and 4.2 series.

Severity
Critical
CVSS
9.8 (3.1)
Published
2019-07-18
CISA KEV
Not currently listed
Ecosystem
software/application
Weaknesses
CWE-122, CWE-787

Affected products

  • facebook / hiphop_virtual_machine
  • facebook / hiphop_virtual_machine / 4.1.0
  • facebook / hiphop_virtual_machine / 4.2.0
  • facebook / hiphop_virtual_machine / 4.3.0
  • facebook / hiphop_virtual_machine / 4.4.0
  • facebook / hiphop_virtual_machine / 4.5.0

Showing 6 representative product identities from 10 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

Buffer bounds, memory safety, and memory corruption

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Identify affected native-code versions, build flags, architectures, parsers, codecs, drivers, and input paths in all shipped artifacts.
  • Determine whether untrusted data reaches the affected routine and the process privilege, sandbox, and network exposure.
  • Confirm statically linked, vendored, firmware, and platform-provided copies, not only package-manager records.

Remediate safely

  • Apply the maintained upstream correction or replace the affected component, then rebuild every dependent artifact from clean inputs.
  • Adopt bounds-checked interfaces, validated sizes and integer conversions, clear ownership, and memory-safe components where practical.
  • Enable supported compiler and runtime hardening and add sanitized tests and fuzz regression seeds derived from non-weaponized fixtures.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.