Skip to content

SIF's Digital Signature Hash Algorithms Not Validated

Moderate severity GitHub Reviewed Published Oct 6, 2022 in sylabs/sif • Updated Feb 17, 2023

Package

gomod github.com/sylabs/sif/v2 (Go)

Affected versions

< 2.8.1

Patched versions

2.8.1

Description

Impact

The github.com/sylabs/sif/v2/pkg/integrity package does not verify that the hash algorithm(s) used are cryptographically secure when verifying digital signatures.

Patches

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

The patch is commit sylabs/sif@07fb860

Workarounds

Users may independently validate that the hash algorithm(s) used for metadata digest(s) and signature hash are cryptographically secure.

References

For more information

If you have any questions or comments about this advisory:

References

@tri-adam tri-adam published to sylabs/sif Oct 6, 2022
Published by the National Vulnerability Database Oct 6, 2022
Published to the GitHub Advisory Database Oct 6, 2022
Reviewed Oct 6, 2022
Last updated Feb 17, 2023

Severity

Moderate

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
Required
Scope
Unchanged
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.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L

EPSS score

0.212%
(60th percentile)

Weaknesses

CVE ID

CVE-2022-39237

GHSA ID

GHSA-m5m3-46gj-wch8

Source code

Credits

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