# CVE-2016-10162: Null dereference in n/a

> Remote attackers can crash PHP applications by sending a malformed WDDX XML document, causing a null pointer dereference.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Jan 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-4m9v-p964-9q24, UBUNTU-CVE-2016-10162

## What is CVE-2016-10162?

CVE-2016-10162 is a high-severity vulnerability in Php Php, published on 24 Jan 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The php_wddx_pop_element function in ext/wddx/wddx.c in PHP 7.0.x before 7.0.15 and 7.1.x before 7.1.1 allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) via an inapplicable class name in a wddxPacket XML document, leading to mishandling in a wddx_deserialize call.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Php Php.

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

Upgrade to a fixed version.

## Is CVE-2016-10162 being exploited?

There is no known exploitation of CVE-2016-10162 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-2016-10162 and fix it if it is affected.

What it is: CVE-2016-10162 is a high-severity vulnerability in Php Php, published on 24 Jan 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-2016-10162 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-2016-10162/ (Markdown: https://insights.sbomify.com/CVE-2016-10162/index.md)
```

## Sources

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

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