# CVE-2017-18190: Auth bypass in n/a

> Remote attackers can execute arbitrary IPP commands via DNS rebinding due to a flawed localhost whitelist, potentially leading to code execution.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2017-18190, DEBIAN-CVE-2017-18190, DLA-1288-1, GHSA-vfqc-qhm9-65mm, MGASA-2018-0147, SUSE-SU-2018:0604-1, UBUNTU-CVE-2017-18190, USN-3577-1

## What is CVE-2017-18190?

CVE-2017-18190 is a high-severity authentication bypass vulnerability in Apple Cups, published on 16 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A localhost.localdomain whitelist entry in valid_host() in scheduler/client.c in CUPS before 2.2.2 allows remote attackers to execute arbitrary IPP commands by sending POST requests to the CUPS daemon in conjunction with DNS rebinding. The localhost.localdomain name is often resolved via a DNS server (neither the OS nor the web browser is responsible for ensuring that localhost.localdomain is 127.0.0.1).

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cups` | SUSE:Linux Enterprise Desktop 12 SP2 | All versions | 1.7.5-20.3.1 |
| `cups` | SUSE:Linux Enterprise Desktop 12 SP3 | All versions | 1.7.5-20.3.1 |
| `cups` | SUSE:Linux Enterprise Server 12 SP1-LTSS | All versions | 1.7.5-20.3.1 |
| `cups` | SUSE:Linux Enterprise Server 12 SP2 | All versions | 1.7.5-20.3.1 |
| `cups` | SUSE:Linux Enterprise Server 12 SP3 | All versions | 1.7.5-20.3.1 |
| `cups` | SUSE:Linux Enterprise Server 12-LTSS | All versions | 1.7.5-20.3.1 |
| `cups` | SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 | All versions | 1.7.5-20.3.1 |
| `cups` | SUSE:Linux Enterprise Server for SAP Applications 12 SP1 | All versions | 1.7.5-20.3.1 |
| `cups` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 1.7.5-20.3.1 |
| `cups` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 1.7.5-20.3.1 |
| `cups` | SUSE:Linux Enterprise Software Development Kit 12 SP2 | All versions | 1.7.5-20.3.1 |
| `cups` | SUSE:Linux Enterprise Software Development Kit 12 SP3 | All versions | 1.7.5-20.3.1 |
| `cups` | SUSE:OpenStack Cloud 6 | All versions | 1.7.5-20.3.1 |

Products: Apple Cups, Canonical Ubuntu Linux, Debian Debian Linux.

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

Upgrade to a fixed version.

## Is CVE-2017-18190 being exploited?

There is no known exploitation of CVE-2017-18190 in the wild and no public exploit code.

## Other vulnerabilities in Apple Cups

- [CVE-2008-5184](https://insights.sbomify.com/CVE-2008-5184/): Cross-site request forgery in n/a (critical 10.0)
- [CVE-2008-3641](https://insights.sbomify.com/CVE-2008-3641/): Memory corruption in n/a (critical 10.0)
- [CVE-2008-0053](https://insights.sbomify.com/CVE-2008-0053/): Memory corruption in n/a (critical 10.0)
- [CVE-2012-6094](https://insights.sbomify.com/CVE-2012-6094/): Missing authorization in cups (critical 9.8)
- [CVE-2010-2941](https://insights.sbomify.com/CVE-2010-2941/): Use after free in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-18190 and fix it if it is affected.

What it is: CVE-2017-18190 is a high-severity authentication bypass vulnerability in Apple Cups, published on 16 Feb 2018. 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-2017-18190 in the wild and no public exploit code.

Affected product: Apple Cups. 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-18190/ (Markdown: https://insights.sbomify.com/CVE-2017-18190/index.md)
```

## Sources

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

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