Sensitive Cookie in HTTPS Session Without 'Secure' Attribute in frontaccountingerp/fa

Valid

Reported on

Oct 14th 2021


✍️ Description

The secure flag is not set for session cookie "PHPSESSID" in the application.

Proof of Concept

Check this for 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.

We created a GitHub Issue asking the maintainers to create a SECURITY.md a year ago
We have contacted a member of the frontaccountingerp/fa team and are waiting to hear back a year ago
frontaccountingerp
a year ago

Maintainer


Indeed , the secure flag is not set. It will be fixed in next FA minor version to be released soon. Thank you for pointing out the problem.

We have sent a second follow up to the frontaccountingerp/fa team. We will try again in 10 days. a year ago
We have sent a third and final follow up to the frontaccountingerp/fa team. This report is now considered stale. a year ago
frontaccountingerp validated this vulnerability a year ago
0x7zed has been awarded the disclosure bounty
The fix bounty is now up for grabs
frontaccountingerp marked this as fixed in 2.4.11 with commit ccca49 a year ago
The fix bounty has been dropped
This vulnerability will not receive a CVE
to join this conversation