Skip to content

vantage6 does not properly delete linked resources when deleting a collaboration

Low severity GitHub Reviewed Published Oct 11, 2023 in vantage6/vantage6 • Updated Nov 5, 2023

Package

pip vantage6 (pip)

Affected versions

< 4.0.0

Patched versions

4.0.0

Description

When a collaboration is deleted in vantage6, the linked resources (such as tasks from that collaboration) are not properly deleted.

This is partly to manage data properly, but also to prevent a potential (but unlikely) side-effect, where if a collaboration with id=10 is deleted, and subsequently a new collaboration is created with id=10, the authenticated users in that collaboration could potentially see results of the deleted collaboration in some cases, resulting in information disclosure.

References

@frankcorneliusmartin frankcorneliusmartin published to vantage6/vantage6 Oct 11, 2023
Published by the National Vulnerability Database Oct 11, 2023
Published to the GitHub Advisory Database Oct 16, 2023
Reviewed Oct 16, 2023
Last updated Nov 5, 2023

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
Local
Attack complexity
High
Privileges required
High
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
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:L/AC:H/PR:H/UI:R/S:C/C:L/I:L/A:N

EPSS score

0.062%
(28th percentile)

Weaknesses

CVE ID

CVE-2023-41881

GHSA ID

GHSA-rf54-7qrr-96j6

Source code

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