Skip to content

GHSA-cmxc-9ghj-jp87 CVE-2022-2997

Insufficient Session Expiration in snipe/snipe-it

Medium Packagist
Severity
4.6 / 10
Medium · CVSS 3.0
Exploit chance (EPSS)
0.93%
Chance of exploitation in the next 30 days. Higher than 60.73% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-384 Session Fixation
Fix
6.0.10
Upgrade snipe/snipe-it to this version or later

Description

Session Fixation in GitHub repository snipe/snipe-it prior to version 6.0.10. The session is not invalidated after a password change.

Affected versions

Packagist

PackageVulnerableFixed in
snipe/snipe-it
< 6.0.10
6.0.10

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

snipe/snipe-it Packagist → 6.0.10

composer
composer require snipe/snipe-it:^6.0.10

Severity breakdown

CVSS 3.0 4.6

CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N

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

Weakness

CWE-384: Session Fixation

Authenticating a user, or otherwise establishing a new user session, without invalidating any existing session identifier gives an attacker the opportunity to steal authenticated sessions.

How to prevent it
  • Architecture and Design: Invalidate any existing session identifiers prior to authorizing a new user session.
  • Architecture and Design: For platforms such as ASP that do not generate new values for sessionid cookies, utilize a secondary cookie. In this approach, set a secondary cookie on the user's browser to a random value and set a session variable to the same value. If the session variable and the cookie value ever don't match, invalidate the session, and force the user to log on again.
  • Operation: Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth [REF-1481].

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-396x-xmvh-p563
Snipe-IT: Stored XSS via Inline XML Rendering in the Uploaded Files API
Medium Also affects snipe/snipe-it
GHSA-p9h3-gvpq-5539
Snipe-IT: Stored XSS via Custom Field name in asset-list column headers
High Also affects snipe/snipe-it
GHSA-hxcx-9h4f-42xx
Snipe-IT: 2FA bypass via the API token flow
High Also affects snipe/snipe-it
GHSA-c8qc-wf67-342w
Snipe-IT: Stored DOM XSS via table selected-count IDs
Medium Also affects snipe/snipe-it
GHSA-r9r3-g9fp-3q4q
Snipe-IT: Maintenance Record Disclosure via Missing Authorization on GET
Medium Also affects snipe/snipe-it
GHSA-3hgv-jr5j-cg9x
Snipe-IT: Chained Information Disclosure and IDOR Leads to Full EULA File Takeover
Medium Also affects snipe/snipe-it
GHSA-c6w2-j4wq-mvwg
Snipe-IT: Tenant Isolation Bypass in FMCS Floater Mode
High Also affects snipe/snipe-it
GHSA-35cr-9hqq-p2mg
Snipe-IT: Cross-company deletion of pending checkout acceptances via unscoped report endpoint
Medium Also affects snipe/snipe-it
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor