# CVE-2017-12934: Use after free in n/a

> A heap use-after-free vulnerability in PHP's unserializer allows attackers to potentially execute arbitrary code or cause denial of service via untrusted data.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Aug 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-cmv9-8x32-p5q7

## What is CVE-2017-12934?

CVE-2017-12934 is a high-severity use after free vulnerability in Php Php, published on 18 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ext/standard/var_unserializer.re in PHP 7.0.x before 7.0.21 and 7.1.x before 7.1.7 is prone to a heap use after free while unserializing untrusted data, related to the zval_get_type function in Zend/zend_types.h. Exploitation of this issue can have an unspecified impact on the integrity of PHP.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2017-12934?

It affects 1 product.


Products: Php Php.

## How do I fix CVE-2017-12934?

Upgrade to a fixed version.

## Is CVE-2017-12934 being exploited?

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

## Other vulnerabilities in Php Php

- [CVE-2012-2688](https://insights.sbomify.com/CVE-2012-2688/): Integer overflow in n/a (critical 10.0)
- [CVE-2012-2376](https://insights.sbomify.com/CVE-2012-2376/): Memory corruption in n/a (critical 10.0)
- [CVE-2011-3268](https://insights.sbomify.com/CVE-2011-3268/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-4143](https://insights.sbomify.com/CVE-2009-4143/): Other in n/a (critical 10.0)
- [CVE-2008-5557](https://insights.sbomify.com/CVE-2008-5557/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-12934 and fix it if it is affected.

What it is: CVE-2017-12934 is a high-severity use after free vulnerability in Php Php, published on 18 Aug 2017. 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-2017-12934 in the wild and no public exploit code.

Affected product: Php Php. 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-2017-12934/ (Markdown: https://insights.sbomify.com/CVE-2017-12934/index.md)
```

## Sources

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

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