# CVE-2017-11143: In PHP before 5.6.31, an invalid free in the WDDX deserialization of boolean parameters could be used by attackers able to inject XML for de


- **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
- **Fix available:** Yes
- **Published:** 10 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-2q66-g93m-c6wv, UBUNTU-CVE-2017-11143

## What is CVE-2017-11143?

CVE-2017-11143 is a high-severity vulnerability in Php Php, published on 10 Jul 2017. 

### Official description

In PHP before 5.6.31, an invalid free in the WDDX deserialization of boolean parameters could be used by attackers able to inject XML for deserialization to crash the PHP interpreter, related to an invalid free for an empty boolean element in ext/wddx/wddx.c.

Weakness: CWE-502 (Deserialization of Untrusted Data), CWE-416 (Use After Free)

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

It affects 1 product.


Products: Php Php.

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

Upgrade to a fixed version.

## Is CVE-2017-11143 being exploited?

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

What it is: CVE-2017-11143 is a high-severity vulnerability in Php Php, published on 10 Jul 2017. 
Exploitation: There is no known exploitation of CVE-2017-11143 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-11143/ (Markdown: https://insights.sbomify.com/CVE-2017-11143/index.md)
```

## Sources

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

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