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

> Attackers can hijack admin sessions via cookie fixation, maintaining access even after password changes on Airtame dongles.

- **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:** No
- **Published:** 15 Oct 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-q3g5-ggf3-c63g

## What is CVE-2017-15304?

CVE-2017-15304 is a critical authentication bypass vulnerability in n/a, published on 15 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

/bin/login.php in the Web Panel on the Airtame HDMI dongle with firmware before 3.0 allows an attacker to set his own session id via a "Cookie: PHPSESSID=" header. This can be used to achieve persistent access to the admin panel even after an admin password change.

Weakness: CWE-384 (Session Fixation)

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

It affects 1 product.


Products: Airtame Hdmi Dongle Firmware.

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

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

## Is CVE-2017-15304 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-7450](https://insights.sbomify.com/CVE-2017-7450/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-15304 is a critical authentication bypass vulnerability in n/a, published on 15 Oct 2017. 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-15304 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-15304/ (Markdown: https://insights.sbomify.com/CVE-2017-15304/index.md)
```

## Sources

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

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