# CVE-2014-6229: Information disclosure in n/a

> Remote attackers can read sensitive memory or bypass cryptographic protections in HHVM due to improper string termination handling.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Dec 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-fgvh-xmpw-4vhf

## What is CVE-2014-6229?

CVE-2014-6229 is a medium-severity vulnerability in n/a, published on 28 Dec 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The HashContext class in hphp/runtime/ext/ext_hash.cpp in Facebook HipHop Virtual Machine (HHVM) before 3.3.0 incorrectly expects that a certain key string uses '\0' for termination, which allows remote attackers to obtain sensitive information by leveraging read access beyond the end of the string, and makes it easier for remote attackers to defeat cryptographic protection mechanisms by leveraging truncation of a string containing an internal '\0' character.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2014-6229?

It affects 1 product.


Products: Facebook Hiphop Virtual Machine.

## How do I fix CVE-2014-6229?

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

## Is CVE-2014-6229 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-3570](https://insights.sbomify.com/CVE-2019-3570/): Memory corruption in HHVM (critical 9.8)
- [CVE-2014-2208](https://insights.sbomify.com/CVE-2014-2208/): Code injection in n/a (high 7.5)
- [CVE-2014-6228](https://insights.sbomify.com/CVE-2014-6228/): Integer overflow in n/a (high 7.5)
- [CVE-2014-2209](https://insights.sbomify.com/CVE-2014-2209/): Privilege escalation in n/a (medium 5.0)
- [CVE-2014-5386](https://insights.sbomify.com/CVE-2014-5386/): Weak cryptography in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-6229 and fix it if it is affected.

What it is: CVE-2014-6229 is a medium-severity vulnerability in n/a, published on 28 Dec 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-6229 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-2014-6229/ (Markdown: https://insights.sbomify.com/CVE-2014-6229/index.md)
```

## Sources

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

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