Skip to content

Old sessions not blocked by login enable function in Snipe-IT

High severity GitHub Reviewed Published Mar 31, 2022 to the GitHub Advisory Database • Updated Jan 27, 2023

Package

composer snipe/snipe-it (Composer)

Affected versions

>= 6.0.0-RC-1, <= 6.0.0-RC-5
< 5.4.2

Patched versions

6.0.0-RC-6
5.4.2

Description

Snipe-IT is a FOSS project for asset management in IT Operations. In Snipe-IT versions 5.4.1 and 6.0.0-RC-5 and prior, active sessions are not revoked when a user account is disabled, allowing that user to still access information that they should no longer be able to. Workarounds include using the KillAllSessions console command, clearing the contents of the storage/framework/sessions directory, or changing the cookie name, but all of those options logout ALL users, which could be kind of annoying. This issue is fixed in versions 6.0.0-RC-6 and 5.4.2.

References

Published by the National Vulnerability Database Mar 30, 2022
Published to the GitHub Advisory Database Mar 31, 2022
Reviewed Apr 1, 2022
Last updated Jan 27, 2023

Severity

High

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
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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.0/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L

EPSS score

0.074%
(33rd percentile)

Weaknesses

CVE ID

CVE-2022-1155

GHSA ID

GHSA-636j-7x7r-gvw2

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.