# CVE-2017-11628: Memory corruption in n/a

> Stack-based buffer overflow in PHP's ini parser allows code execution or denial of service when applications parse untrusted ini strings.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 25 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DLA-1066-1, GHSA-v28p-49px-6723, UBUNTU-CVE-2017-11628

## What is CVE-2017-11628?

CVE-2017-11628 is a high-severity memory corruption vulnerability in Php Php, published on 25 Jul 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

In PHP before 5.6.31, 7.x before 7.0.21, and 7.1.x before 7.1.7, a stack-based buffer overflow in the zend_ini_do_op() function in Zend/zend_ini_parser.c could cause a denial of service or potentially allow executing code. NOTE: this is only relevant for PHP applications that accept untrusted input (instead of the system's php.ini file) for the parse_ini_string or parse_ini_file function, e.g., a web application for syntax validation of php.ini directives.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Php Php.

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

Upgrade to a fixed version.

## Is CVE-2017-11628 being exploited?

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

What it is: CVE-2017-11628 is a high-severity memory corruption vulnerability in Php Php, published on 25 Jul 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-11628 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-11628/ (Markdown: https://insights.sbomify.com/CVE-2017-11628/index.md)
```

## Sources

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

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