CVE-2019-19724
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInsecure 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSingularity container runtime creates the $HOME/.singularity directory with overly permissive 777 permissions (world-readable/writable) in versions 3.3.0 through 3.5.1. This allows any local user on the system to access, read, and modify files in this directory, potentially exposing sensitive information such as authentication tokens for Sylabs cloud services and allowing attackers to tamper with configuration to redirect cloud operations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 3.3.0, <= 3.5.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Singularity versionRun 'singularity --version' or 'singularity version' to get the installed version numberAffected if Version is 3.3.0, 3.3.0-rc.1, 3.3.0-rc.2, 3.4.0, 3.4.1, 3.4.2, 3.4.3, 3.5.0, or 3.5.1 (any version from 3.3.0 through 3.5.1 inclusive)
-
Locate the .singularity directoryRun 'ls -la $HOME/.singularity' to check if the directory exists in the user's home folderAffected if The .singularity directory exists in the user's home directory
-
Verify directory permissionsInspect the permission bits in the ls -la output - look for 'drwxrwxrwx' which indicates 777 permissionsAffected if Permissions show 'drwxrwxrwx' (777) or 'rwxrwxrwx' meaning world-readable and world-writable access
-
Confirm vulnerability conditionIf version is affected AND .singularity exists with 777 permissions, the system is vulnerableAffected if Both the affected version range applies AND the .singularity directory has 777 permissions
A system is affected if Singularity version 3.3.0 through 3.5.1 is installed AND the $HOME/.singularity directory exists with world-readable/writable (777) permissions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Singularity to version 3.5.2 or later, which sets secure permissions (700) on the .singularity directory. Alternatively, manually run 'chmod 700 $HOME/.singularity' on affected systems as an immediate workaround.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19724 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-19724 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data