Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Create cookie cached on disk bcheck #81

Merged
merged 3 commits into from
Aug 11, 2023
Merged

Create cookie cached on disk bcheck #81

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ee17307
Create cookie cached on disk
domwhewell-sage Aug 11, 2023
ca9dd47
Corrected spelling mistake
domwhewell-sage Aug 11, 2023
4e00778
Made suggested changes
domwhewell-sage Aug 11, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions other/tokens/cookie-cached-on-disk.bcheck
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
metadata:
language: v1-beta
name: "Cookie cached on disk"
description: "Checks if cookies are cached on disk"
tags: "passive"

given response then
if {latest.response} matches "(?i)Set-Cookie:.+(expires=[\w\d\s:,]+;|max-age=\d+;).*" then
report issue:
severity: info
confidence: certain
detail: "Cookies are set that have an expires or max-age attribute, these are considered persistent cookies and will be stored on disk by the web browser until the expiration time. Check to ensure these are not used to maintain the login session as if an authenticated user does not click the logout button and instead closes the browser, the session will resume when the browser is re-opened. If an attacker has access to the filesystem location where the web browser cache is stored the session cookie could be extracted and used to authenticate the attacker to the web application. If it is a shared machine another user could authenticate themselves just by re-opening the browser."
remediation: "Session management tokens should make use of non-persistent cookies. This forces the session to disappear from the client if the current web browser is closed. Therefore the expires or max-age attribute should be removed from the session cookie. https://cheatsheetseries.owasp.org/cheatsheets/Session_Management_Cheat_Sheet.html#expire-and-max-age-attributes"
end if