fix(deps): update dependency @fastify/secure-session to v7 [security] #438
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
6.2.0
->7.3.0
GitHub Vulnerability Alerts
CVE-2024-31999
Impact
At the end of the request handling, it will encrypt all data in the session with a secret key and attach the ciphertext as a cookie value with the defined cookie name. After that, the session on the server side is destroyed. When an encrypted cookie with matching session name is provided with subsequent requests, it will decrypt the ciphertext to get the data. The plugin then creates a new session with the data in the ciphertext. Thus theoretically the web instance is still accessing the data from a server-side session, but technically that session is generated solely from a user provided cookie (which is assumed to be non-craftable because it is encrypted with a secret key not known to the user).
The issue exists in the session removal process. In the delete function of the code, when the session is deleted, it is marked for deletion. However, if an attacker could gain access to the cookie, they could keep using it forever.
Patches
Fixed in 56d66642ecc633cff0606927601e81cdac361370.
Update to v7.3.0.
Workarounds
Include a "last update" field in the session, and treat "old sessions" as expired.
Make sure to configure your cookie as "http only".
References
Release Notes
fastify/fastify-secure-session (@fastify/secure-session)
v7.3.0
Compare Source
Fixes GHSA-9wwp-q7wq-jx35
What's Changed
New Contributors
Full Changelog: fastify/fastify-secure-session@v7.2.0...v7.3.0
v7.1.0
Compare Source
What's Changed
New Contributors
Full Changelog: fastify/fastify-secure-session@v7.0.0...v7.1.0
v7.0.0
Compare Source
What's Changed
New Contributors
Full Changelog: fastify/fastify-secure-session@v6.2.0...v7.0.0
Configuration
📅 Schedule: Branch creation - "" in timezone Europe/Paris, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.