# CVE-2017-7272: Server-side request forgery in n/a

> An attacker can bypass port restrictions in PHP applications using fsockopen by specifying a port in the hostname argument, leading to Server-Side Request Forgery.

- **Severity:** High 7.4 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-943r-xvqq-r4rh, SUSE-SU-2017:1709-1, UBUNTU-CVE-2017-7272

## What is CVE-2017-7272?

CVE-2017-7272 is a high-severity server-side request forgery vulnerability in Php Php, published on 27 Mar 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

PHP through 7.1.11 enables potential SSRF in applications that accept an fsockopen or pfsockopen hostname argument with an expectation that the port number is constrained. Because a :port syntax is recognized, fsockopen will use the port number that is specified in the hostname argument, instead of the port number in the second argument of the function.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `php53` | SUSE:Linux Enterprise Server 11 SP4 | All versions | 5.3.17-111.2 |
| `php53` | SUSE:Linux Enterprise Server for SAP Applications 11 SP4 | All versions | 5.3.17-111.2 |
| `php53` | SUSE:Linux Enterprise Software Development Kit 11 SP4 | All versions | 5.3.17-111.2 |

Products: Php Php.

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

Upgrade to a fixed version.

## Is CVE-2017-7272 being exploited?

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

What it is: CVE-2017-7272 is a high-severity server-side request forgery vulnerability in Php Php, published on 27 Mar 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-7272 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-7272/ (Markdown: https://insights.sbomify.com/CVE-2017-7272/index.md)
```

## Sources

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

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