# CVE-2019-19724: Singularity insecure permissions

> Insecure directory permissions in Singularity allow attackers to leak information and redirect cloud service operations.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 18 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mj73-5x75-9phh, openSUSE-SU-2020:0057-1

## What is CVE-2019-19724?

CVE-2019-19724 is a high-severity vulnerability in n/a, published on 18 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Insecure permissions (777) are set on $HOME/.singularity when it is newly created by Singularity (version from 3.3.0 to 3.5.1), which could lead to an information leak, and malicious redirection of operations performed against Sylabs cloud services.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2019-19724?

2 open source packages ship an affected version, including github.com/sylabs/singularity. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/sylabs/singularity` | Go | From 3.3.0 | 3.5.2 |
| `github.com/sylabs/singularity` | Go | From 3.3.0 | 3.5.2 |
| `singularity` | openSUSE:Leap 15.1 | All versions | 2.6.1-lp151.2.3.1 |

Products: Sylabs Singularity.

## How do I fix CVE-2019-19724?

Upgrade github.com/sylabs/singularity to 3.5.2 or later.

## Is CVE-2019-19724 being exploited?

There is no known exploitation of CVE-2019-19724 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-2019-19724 and fix it if it is affected.

What it is: CVE-2019-19724 is a high-severity vulnerability in n/a, published on 18 Dec 2019. 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-2019-19724 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/sylabs/singularity (Go): affected from 3.3.0; fixed in 3.5.2
- github.com/sylabs/singularity (Go): affected from 3.3.0; fixed in 3.5.2

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-2019-19724/ (Markdown: https://insights.sbomify.com/CVE-2019-19724/index.md)
```

## Sources

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

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