Skip to content

vantage6 may create unencrypted tasks in encrypted collaboration

Low severity GitHub Reviewed Published Jan 30, 2024 in vantage6/vantage6 • Updated Feb 8, 2024

Package

pip vantage6 (pip)

Affected versions

< 4.2.0

Patched versions

4.2.0

Description

Impact

There are no checks on whether the input is encrypted if a task is created in an encrypted collaboration. Therefore, a user may accidentally create a task with sensitive input data that will then be stored unencrypted in a database.

Workarounds

This is not an issue with the normal workflow, only if e.g. a user with the python client sets encryption to the wrong value.

References

@bartvanb bartvanb published to vantage6/vantage6 Jan 30, 2024
Published by the National Vulnerability Database Jan 30, 2024
Published to the GitHub Advisory Database Jan 30, 2024
Reviewed Jan 30, 2024
Last updated Feb 8, 2024

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
Low
Privileges required
Low
User interaction
Required
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:L/PR:L/UI:R/S:U/C:L/I:N/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(42nd percentile)

Weaknesses

Insecure Storage of Sensitive Information

The product stores sensitive information without properly limiting read or write access by unauthorized actors. Learn more on MITRE.

CVE ID

CVE-2024-22193

GHSA ID

GHSA-rjmv-52mp-gjrr

Source code

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