Predictable UUIDs via insecure dependency randomness
Published May 7, 2021 · Updated Aug 3, 2024
Insufficient randomness in Sylabs SIF 1.2.2 and earlier allows attackers to predict UUIDs via newly created container images. The siftool new command and siftool.New function delegate UUID generation to satori/go.uuid v1.2.0, whose NewV4 output can contain large predictable zero-filled regions. Exploitation requires access to a generated SIF identifier; published evidence establishes weakened identifier unpredictability, not code execution or direct data access.
Summary
What happened
Insufficient randomness in Sylabs SIF 1.2.2 and earlier allows attackers to predict UUIDs via newly created container images. The siftool new command and siftool.New function delegate UUID generation to satori/go.uuid v1.2.0, whose NewV4 output can contain large predictable zero-filled regions. Exploitation requires access to a generated SIF identifier; published evidence establishes weakened identifier unpredictability, not code execution or direct data access.
The record
- CVE
- CVE-2021-29499
- Published
- May 7, 2021
- Updated
- Aug 3, 2024
- Vendor
- Sylabs
- Product
- Singularity Image Format (SIF)
- Classifications
- CWE-330
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 7, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=<= 1.2.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo