You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Missing HttpOnly and Secure Attribute in Session Cookie
The console-session cookie is missing the HttpOnly and Secure attributes. This allows it to be accessed by external client-side scripts.
Reference: https://www.owasp.org/index.php/HttpOnly
Cacheable HTTPS Response
Some browsers, including Internet Explorer, cache content accessed via HTTPS. If sensitive information in application responses is stored in the local cache, then this may be retrieved by other users who have access to the same system at a future time.
Ideally, the web server should return the following HTTP headers in all responses containing sensitive content:
1- Cache-control: no-store
2- Pragma: no-cache
Example of an affected route: https://my.console:4443/pp/v1/auth/session/verify
Both of these issues are present on the all-in-one docker deployment.
The text was updated successfully, but these errors were encountered:
Ok, I've had a brief look into this and will probably need to bring in a few other people. Until then here's my initial findings.
HttpOnly, and Secure, should be set across all deployments as they go through the same session cookie path. Running in docker-compose (which is the same as in k8) successfully adds them however they're missing from both all-in-one and CF app deployment types. We'll need to investigate why the same process isn't applied to both.
For cache-control, we do add no-cache for static content in docker-compose and k8 but not for any jetstream requests (neither jetstream specific or proxied to a CF). What I think we'll need to do...
Add cache-control: no-cache to jetstream static file requests (this is only missing in types all-in-one and CF app)
Add cache-control: no-store to all non-static requests, or at least /auth and endpoint proxies.
For pragma, it looks like this is a client side specific request header and is not something we need to add to the response header.
@colton-nicotera Thanks for raising this issue. We've addressed this in the following changes..
Session Cookies... #2911 + nwmac/sqlitestore#3
Caching... #2910
If you continue to see this issue or have any further questions please just let us know.
Missing HttpOnly and Secure Attribute in Session Cookie
The
console-session
cookie is missing the HttpOnly and Secure attributes. This allows it to be accessed by external client-side scripts.Reference: https://www.owasp.org/index.php/HttpOnly
Cacheable HTTPS Response
Some browsers, including Internet Explorer, cache content accessed via HTTPS. If sensitive information in application responses is stored in the local cache, then this may be retrieved by other users who have access to the same system at a future time.
Ideally, the web server should return the following HTTP headers in all responses containing sensitive content:
1- Cache-control: no-store
2- Pragma: no-cache
Example of an affected route: https://my.console:4443/pp/v1/auth/session/verify
Both of these issues are present on the all-in-one docker deployment.
The text was updated successfully, but these errors were encountered: