Sensitive Cookie in HTTPS Session Without 'Secure' Attribute in spiral-project/ihatemoney

Valid

Reported on

Sep 18th 2021

Description

Secure flag is not implemented on the application

Proof of Concept

https://drive.google.com/file/d/10p4ejCFsLA6LO32nPNTRKqZjlqVHVpUf/view?usp=sharing

Impact

The secure flag is an option that can be set by the application server when sending a new cookie to the user within an HTTP Response. The purpose of the secure flag is to prevent cookies from being observed by unauthorized parties due to the transmission of a the cookie in clear text. To accomplish this goal, browsers which support the secure flag will only send cookies with the secure flag when the request is going to a HTTPS page. Said in another way, the browser will not send a cookie with the secure flag set over an unencrypted HTTP request. By setting the secure flag, the browser will prevent the transmission of a cookie over an unencrypted channel.

We have contacted a member of the spiral-project/ihatemoney team and are waiting to hear back 2 years ago
A spiral-project/ihatemoney maintainer validated this vulnerability 2 years ago
0xdhinu has been awarded the disclosure bounty
The fix bounty is now up for grabs
A spiral-project/ihatemoney maintainer marked this as fixed with commit e626a1 2 years ago
The fix bounty has been dropped
This vulnerability will not receive a CVE
to join this conversation