# CVE-2016-6874: The array_*_recursive functions in Facebook HHVM before 3.15.0 allows attackers to have unspecified impact via unknown vectors, related to recursion.


- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Feb 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-6688-425h-xgq3, UBUNTU-CVE-2016-6874

## What is CVE-2016-6874?

CVE-2016-6874 is a critical vulnerability in n/a, published on 17 Feb 2017. 

### Official description

The array_*_recursive functions in Facebook HHVM before 3.15.0 allows attackers to have unspecified impact via unknown vectors, related to recursion.

## Which versions are affected by CVE-2016-6874?

It affects 1 product.


Products: Facebook Hhvm.

## How do I fix CVE-2016-6874?

No fix has been published for CVE-2016-6874 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-6874 being exploited?

There is no known exploitation of CVE-2016-6874 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2022-36937](https://insights.sbomify.com/CVE-2022-36937/): HHVM 4.172.0 and all prior versions use TLS 1.0 for secure connections when handling tls:// URLs in the stream extension. (critical 9.8)
- [CVE-2020-1900](https://insights.sbomify.com/CVE-2020-1900/): Use after free in HHVM (critical 9.8)
- [CVE-2020-1916](https://insights.sbomify.com/CVE-2020-1916/): Integer overflow in HHVM (critical 9.8)
- [CVE-2020-1917](https://insights.sbomify.com/CVE-2020-1917/): Memory corruption in HHVM (critical 9.8)
- [CVE-2021-24025](https://insights.sbomify.com/CVE-2021-24025/): Integer overflow in HHVM (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-6874 and fix it if it is affected.

What it is: CVE-2016-6874 is a critical vulnerability in n/a, published on 17 Feb 2017. 
Exploitation: There is no known exploitation of CVE-2016-6874 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-6874/ (Markdown: https://insights.sbomify.com/CVE-2016-6874/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-6874
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-6874
- OSV: https://osv.dev/vulnerability/CVE-2016-6874

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-6874/
Summaries are generated and may contain mistakes; the official description above is the record.