# CVE-2020-13847: Other in n/a

> Singularity fails to verify integrity of SIF file metadata, allowing attackers to bypass signature checks and potentially execute malicious containers.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Jul 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-m7j2-9565-4h9v, UBUNTU-CVE-2020-13847

## What is CVE-2020-13847?

CVE-2020-13847 is a high-severity vulnerability in n/a, published on 14 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-354 (Improper Validation of Integrity Check Value)

## Which versions are affected by CVE-2020-13847?

It affects 1 product.


Products: Sylabs Singularity.

## How do I fix CVE-2020-13847?

Upgrade to a fixed version.

## Is CVE-2020-13847 being exploited?

There is no known exploitation of CVE-2020-13847 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2021-33027](https://insights.sbomify.com/CVE-2021-33027/): Weak cryptography in n/a (critical 9.8)
- [CVE-2021-33622](https://insights.sbomify.com/CVE-2021-33622/): Other in n/a (critical 9.8)
- [CVE-2018-19295](https://insights.sbomify.com/CVE-2018-19295/): Sylabs Singularity Improper Input Validation (high 7.8)
- [CVE-2020-13845](https://insights.sbomify.com/CVE-2020-13845/): Execution Control List (ECL) Is Insecure in Singularity (high 7.5)
- [CVE-2020-13846](https://insights.sbomify.com/CVE-2020-13846/): "Verify All" Returns Success Despite Validation Failures in Singularity (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-13847 and fix it if it is affected.

What it is: CVE-2020-13847 is a high-severity vulnerability in n/a, published on 14 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-13847 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-13847/ (Markdown: https://insights.sbomify.com/CVE-2020-13847/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-13847
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-13847
- OSV: https://osv.dev/vulnerability/CVE-2020-13847

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-13847/
Summaries are generated and may contain mistakes; the official description above is the record.