CVE-2017-15304
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · unedited/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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA session fixation vulnerability in /bin/login.php of Airtame HDMI dongle firmware before 3.0 allows attackers to set a fixed PHPSESSID cookie value before authentication. Once an admin logs in using this attacker-controlled session ID, the attacker gains persistent admin panel access that persists even after password changes, since the session remains valid while the underlying credentials are not tied to the session.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2.3.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed firmware versionAccess the Airtame admin panel or check the device settings to view the current firmware version number. This is typically found in Settings > About or a similar location within the web interface.Affected if The firmware version displayed is 2.3.3 or lower
-
Locate the login scriptAttempt to access the file /bin/login.php on the Airtame device via the web interface or by examining the firmware filesystem if you have access to a firmware dump.Affected if The file /bin/login.php exists and is accessible, indicating the vulnerable script is present
-
Verify PHP session configurationExamine the PHP configuration on the device (php.ini) or inspect the login.php source code to check if session ID regeneration is implemented. Look for calls to session_regenerate_id() before or during the authentication process.Affected if No session_regenerate_id() call is found in the login flow, meaning session IDs are not being regenerated on login
-
Test session fixation behaviorSet a custom PHPSESSID cookie value before attempting to log in, then authenticate as an admin. After successful login, examine the PHPSESSID cookie value to determine if it remains unchanged from the attacker-controlled value.Affected if The PHPSESSID cookie value remains identical to the value you set before authentication, confirming session fixation is possible
-
Check session invalidation on password changeAs an admin, change the account password. Then attempt to access the admin panel using the previously established session (with the fixed PHPSESSID) without re-authenticating.Affected if The session remains valid and admin access persists after the password change, indicating sessions are not invalidated when credentials change
You are affected if your Airtame firmware is version 2.3.3 or lower and the session ID is not regenerated during login, allowing persistent admin access via session fixation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Airtame firmware to version 3.0 or later, which implements proper session ID regeneration on login and invalidates existing sessions on password changes.
Firmware version 3.0 or later
- Obtain the official Airtame firmware version 3.0 or later from the vendor's official distribution channel
- Access the Airtame device administration interface
- Navigate to the firmware update or system settings section
- Upload and apply the firmware version 3.0 or newer
- Verify the firmware version after update to confirm the fix is applied
- Ensure default session configurations are in place by logging out and logging back in
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-15304 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-15304 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data