Skip to content

Using Local Storage to Store Session Token

Low
mlodic published GHSA-cjrq-vmxr-6h86 Mar 28, 2024

Package

intelowlproject (DockerHub)

Affected versions

>=4.0.0,<=6.0.0

Patched versions

>=6.0.0

Description

Consider not storing the session token in the users' local storage.
Consider setting the session token as a cookie with the "HTTPOnly", "Secure" and “SameSite”. An Anti-CSRF header token is potentially required as well in order to prevent CSRF attacks when using session cookies.

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

CVE ID

No known CVE

Weaknesses

No CWEs