Skip to content
Fencer Vulns
high 7.5

CVE-2021-29499 json

Predictable SIF UUID Identifiers

published 2021-05-07 5 y ago modified 2026-07-08 4 mo ago also GHSA-4gh8-x3vv-phhg , GO-2022-0912 , EUVD-2021-0940

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

Summary

SIF is an open source implementation of the Singularity Container Image Format. 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. A patch is available in version >= v1.2.3 of the module. Users are encouraged to upgrade. As a workaround, 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.

Patch / fix

  • go github.com/sylabs/sif 1.2.3
  • sylabs singularity_image_format 1.2.3
  • golang-github-sylabs-sif Debian 14, Debian 13, Debian 12 2.3.1-2

debian advisories DEBIAN-CVE-2021-29499

Exploit prediction

0.96% chance of exploitation in the next 30 days, higher than 61% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/sylabs/sif/security/advisories/GHSA-4gh8-x3vv-phhg referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:P/I:N/A:N
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected packages

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

Affected products

  • sylabs sif

Classification

Weakness
  • CWE-330 Use of Insufficiently Random Values
  • CWE-340 Generation of Predictable Numbers or Identifiers

References

Sources

Fencer Vulns 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.