Sensitive Cookie in HTTPS Session Without 'Secure' Attribute in erudika/para
Jul 14th 2022
The Secure attribute for sensitive cookies in HTTPS sessions is not set, which could cause the user agent to send those cookies in plaintext over an HTTP session.
Proof of Concept
If possible, you should set the Secure flag for these cookies.
When a cookie is set with the Secure flag, it instructs the browser that the cookie can only be accessed over secure SSL/TLS channels. This is an important security protection for session cookies. The secure flag should be set on all cookies that are used for transmitting sensitive data when accessing content over HTTPS. If cookies are used to transmit session tokens, then areas of the application that are accessed over HTTPS should employ their own session handling mechanism, and the session tokens used should never be transmitted over unencrypted communications.
The cookie (para-auth) is yet not fixed. Once the case is solved, are you happy to assign a CVE for this one?? @maintainer @admin