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

> Physically proximate attackers can bypass UI restrictions via the print dialog to gain administrative privileges and network access on the kiosk's Windows OS.

- **Severity:** Medium 6.6 (`CVSS:3.0/AV:P/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Feb 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jp2p-37cw-qg8c

## What is CVE-2017-5634?

CVE-2017-5634 is a medium-severity authentication bypass vulnerability in n/a, published on 9 Feb 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Norwegian Air Shuttle (aka norwegian.com) airline kiosk allows physically proximate attackers to bypass the intended "Please select booking identification" UI step, and obtain administrative privileges and network access on the underlying Windows OS, by accessing a touch-screen print icon to manipulate the print dialog.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere)

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

It affects 1 product.


Products: Norwegian-Air Norwegian Air Kiosk.

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

No fix has been published for CVE-2017-5634 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-5634 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-5634 is a medium-severity authentication bypass vulnerability in n/a, published on 9 Feb 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-5634 in the wild and no public exploit code.

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

## Sources

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

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