Skip to content

Predictable SIF UUID Identifiers in github.com/sylabs/sif

High severity GitHub Reviewed Published May 7, 2021 in sylabs/sif • Updated Feb 3, 2023

Package

gomod github.com/sylabs/sif (Go)

Affected versions

< 1.2.3

Patched versions

1.2.3

Description

Impact

The siftool new command and func siftool.New() produce predictable UUID identifiers due to insecure randomness in the version of the github.com/satori/go.uuid module used as a dependency.

Patches

A patch is available in version >= v1.2.3 of the module. Users are encouraged to upgrade.

The patch is commit sylabs/sif@1939628

Workarounds

Users passing CreateInfo struct should ensure the ID field is generated using a version of github.com/satori/go.uuid that is not vulnerable to this issue. Unfortunately, the latest tagged release is vulnerable to this issue. One way to obtain a non-vulnerable version is:

go get github.com/satori/go.uuid@75cca531ea763666bc46e531da3b4c3b95f64557

References

For more information

If you have any questions or comments about this advisory:

References

@tri-adam tri-adam published to sylabs/sif May 7, 2021
Reviewed May 7, 2021
Published by the National Vulnerability Database May 7, 2021
Published to the GitHub Advisory Database May 18, 2021
Last updated Feb 3, 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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
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:N/UI:N/S:U/C:N/I:H/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.
(54th percentile)

Weaknesses

Use of Insufficiently Random Values

The product uses insufficiently random numbers or values in a security context that depends on unpredictable numbers. Learn more on MITRE.

Generation of Predictable Numbers or Identifiers

The product uses a scheme that generates numbers or identifiers that are more predictable than required. Learn more on MITRE.

CVE ID

CVE-2021-29499

GHSA ID

GHSA-4gh8-x3vv-phhg

Source code

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