Sensitive Cookie in HTTPS Session Without 'Secure' Attribute in azuracast/azuracast


Reported on

Aug 26th 2021

✍️ Description

The secure flag is not set for app_session cookie in the application.

🕵️‍♂️ Proof of Concept

PoC Image:

💥 Impact

If the secure flag is set on a cookie, then browsers will not submit the cookie in any requests that use an unencrypted HTTP connection, thereby preventing the cookie from being trivially intercepted by an attacker monitoring network traffic. If the secure flag is not set, then the cookie will be transmitted in clear-text if the user visits any HTTP URLs within the cookie's scope. An attacker may be able to induce this event by feeding a user suitable links, either directly or via another web site.


2 years ago


Hey Melbin, I've just emailed the repo's maintainers for you. Waiting to hear back, good job!

We have contacted a member of the azuracast team and are waiting to hear back 2 years ago
Buster Neece validated this vulnerability 2 years ago
Melbin Mathew Antony has been awarded the disclosure bounty
The fix bounty is now up for grabs
Buster Neece
2 years ago

We've applied a selective fix for this issue in the latest Rolling Release version of AzuraCast. See the following commit for details:

The "secure only" flag on the cookie is only set if two factors are true:

  • if the user has selected the "Require HTTPS" setting, and
  • if the user is currently on a page with an HTTPS URL.

If these two settings are true, then we can reliably guarantee that the user intends to connect solely via HTTPS to their web application, so the "secure only" flag on the session cookie will cause no side effects.

Buster Neece marked this as fixed with commit 95a9b8 2 years ago
Buster Neece has been awarded the fix bounty
This vulnerability will not receive a CVE
to join this conversation