# CVE-2018-7584: Memory corruption in n/a

> A stack-based buffer under-read in PHP's HTTP response parsing allows attackers to cause denial of service or potentially execute arbitrary code.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 1 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2018-7584, DLA-1326-1, GHSA-w5h8-6928-2j67, MGASA-2018-0167, SUSE-SU-2018:0646-1, SUSE-SU-2018:0717-1, UBUNTU-CVE-2018-7584

## What is CVE-2018-7584?

CVE-2018-7584 is a critical memory corruption vulnerability in Canonical Ubuntu Linux, published on 1 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In PHP through 5.6.33, 7.0.x before 7.0.28, 7.1.x through 7.1.14, and 7.2.x through 7.2.2, there is a stack-based buffer under-read while parsing an HTTP response in the php_stream_url_wrap_http_ex function in ext/standard/http_fopen_wrapper.c. This subsequently results in copying a large string.

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

## Which versions are affected by CVE-2018-7584?

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `php5` | SUSE:Linux Enterprise Module for Web and Scripting 12 | All versions | 5.5.14-109.24.1 |
| `php7` | SUSE:Linux Enterprise Module for Web and Scripting 12 | All versions | 7.0.7-50.32.1 |
| `php5` | SUSE:Linux Enterprise Software Development Kit 12 SP2 | All versions | 5.5.14-109.24.1 |
| `php7` | SUSE:Linux Enterprise Software Development Kit 12 SP2 | All versions | 7.0.7-50.32.1 |
| `php5` | SUSE:Linux Enterprise Software Development Kit 12 SP3 | All versions | 5.5.14-109.24.1 |
| `php7` | SUSE:Linux Enterprise Software Development Kit 12 SP3 | All versions | 7.0.7-50.32.1 |

Products: Canonical Ubuntu Linux, Debian Debian Linux, Php Php.

## How do I fix CVE-2018-7584?

Upgrade to a fixed version.

## Is CVE-2018-7584 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-7584 exists.

Public exploit code:

- PHP 7.2.2 - 'php_stream_url_wrap_http_ex' Buffer Overflow (exploitdb)

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-7584 and fix it if it is affected.

What it is: CVE-2018-7584 is a critical memory corruption vulnerability in Canonical Ubuntu Linux, published on 1 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-7584 exists.

Affected product: Canonical Ubuntu Linux. 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-2018-7584/ (Markdown: https://insights.sbomify.com/CVE-2018-7584/index.md)
```

## Sources

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

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