Skip to content
Fencer Intel
medium 6.3

CVE-2022-39237 json

Digital Signature Hash Algorithms Not Validated in sylabs/sif

published 4y ago modified 4mo ago also GHSA-m5m3-46gj-wch8 , GO-2022-1045 , EUVD-2022-7123

cvss
6.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 51%
public exploits
0
none known

Summary

syslabs/sif is the Singularity Image Format (SIF) reference implementation. In versions prior to 2.8.1the `github.com/sylabs/sif/v2/pkg/integrity` package did not verify that the hash algorithm(s) used are cryptographically secure when verifying digital signatures. A patch is available in version >= v2.8.1 of the module. Users are encouraged to upgrade. Users unable to upgrade may independently validate that the hash algorithm(s) used for metadata digest(s) and signature hash are cryptographically secure.

Patch / fix

  • go github.com/sylabs/sif/v2 2.8.1
  • sylabs singularity_image_format 2.8.1
  • golang-github-sylabs-sif Debian 14, Debian 13, Debian 12 2.8.3-1

debian advisories DEBIAN-CVE-2022-39237

  • singularity-ce openSUSE Tumbleweed 4.1.3-1.1
  • apptainer openSUSE Tumbleweed 1.1.2-1.1
  • apptainer openSUSE Leap 15.4 1.1.2-lp154.2.1

opensuse advisories openSUSE-SU-2024:14059-1openSUSE-SU-2024:12389-1openSUSE-SU-2023:0018-1

  • apptainer Alpine 3.24, Alpine 3.23, Alpine 3.22 +3 more 1.1.2-r0

alpine advisories ALPINE-CVE-2022-39237

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2022-39237 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.65% chance of exploitation in the next 30 days, higher than 51% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 6.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub 3.1 6.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L

Affected packages

ecosystem package affected fixed in
go github.com/sylabs/sif/v2
<2.8.1
2.8.1

Affected products

  • sylabs sif

Classification

Weakness
  • CWE-347 Improper Verification of Cryptographic Signature
  • CWE-327 Use of a Broken or Risky Cryptographic Algorithm

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.