Signature trust bypass via weak hash acceptance
Published Oct 6, 2022 · Updated Apr 23, 2025
Improper signature verification in Sylabs SIF before 2.8.1 allows local users to pass images signed with weak hash algorithms. The pkg/integrity verification paths accepted SHA-1 metadata digests and OpenPGP signatures instead of restricting hashes to an approved set. Exploitation requires a user or consuming application to verify attacker-controlled SIF content, weakening trust in image integrity without directly executing code.
Summary
What happened
Improper signature verification in Sylabs SIF before 2.8.1 allows local users to pass images signed with weak hash algorithms. The pkg/integrity verification paths accepted SHA-1 metadata digests and OpenPGP signatures instead of restricting hashes to an approved set. Exploitation requires a user or consuming application to verify attacker-controlled SIF content, weakening trust in image integrity without directly executing code.
The record
- CVE
- CVE-2022-39237
- Published
- Oct 6, 2022
- Updated
- Apr 23, 2025
- Vendor
- Sylabs
- Product
- Singularity Image Format (SIF)
- Classifications
- CWE-328, CWE-347, T1553.002
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Oct 6, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record 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=< 2.8.1
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