{"answers":{"affected":"2 open source packages ship an affected version, including github.com/sylabs/singularity. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-19724 in the wild and no public exploit code.","fix":"Upgrade github.com/sylabs/singularity to 3.5.2 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2019-19724 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2019-19724 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/sylabs/singularity (Go): affected from 3.3.0; fixed in 3.5.2\n- github.com/sylabs/singularity (Go): affected from 3.3.0; fixed in 3.5.2\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2019-19724/ (Markdown: https://insights.sbomify.com/CVE-2019-19724/index.md)","id":"CVE-2019-19724","markdown":"https://insights.sbomify.com/CVE-2019-19724/index.md","name":"CVE-2019-19724","record":{"aliases":["GHSA-mj73-5x75-9phh","openSUSE-SU-2020:0057-1"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Singularity container runtime","requires_auth":"none","summary":"Insecure directory permissions in Singularity allow attackers to leak information and redirect cloud service operations.","user_interaction":"not_required","vuln_class":"misconfiguration"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"singularity","vendor":"sylabs"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-276","name":"Incorrect Default Permissions"}],"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.","ecosystems":["Go","openSUSE:Leap 15.1"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Singularity insecure permissions","id":"CVE-2019-19724","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"misconfiguration","year":"2019"},"n_packages":3,"n_references":3,"next":{"headline":"Use after free in n/a","id":"CVE-2019-19725"},"packages":[{"ecosystem":"Go","fixed":["3.5.2"],"introduced":["3.3.0"],"last_affected":[],"package":"github.com/sylabs/singularity","purl":null,"source":"GHSA-mj73-5x75-9phh"},{"ecosystem":"Go","fixed":["3.5.2"],"introduced":["3.3.0"],"last_affected":[],"package":"github.com/sylabs/singularity","purl":"pkg:golang/github.com/sylabs/singularity","source":"GHSA-mj73-5x75-9phh"},{"ecosystem":"openSUSE:Leap 15.1","fixed":["2.6.1-lp151.2.3.1"],"introduced":["0"],"last_affected":[],"package":"singularity","purl":"pkg:rpm/opensuse/singularity\u0026distro=openSUSE%20Leap%2015.1","source":"openSUSE-SU-2020:0057-1"}],"prev":{"headline":"Null dereference in n/a","id":"CVE-2019-19722"},"products":["n/a"],"published":"2019-12-18","related":[{"cvss_score":9.8,"headline":"Weak cryptography in n/a","id":"CVE-2021-33027","kev_date_added":null,"published":"2021-07-19"},{"cvss_score":9.8,"headline":"Other in n/a","id":"CVE-2021-33622","kev_date_added":null,"published":"2021-06-15"},{"cvss_score":7.8,"headline":"Sylabs Singularity Improper Input Validation","id":"CVE-2018-19295","kev_date_added":null,"published":"2018-12-17"},{"cvss_score":7.5,"headline":"Execution Control List (ECL) Is Insecure in Singularity","id":"CVE-2020-13845","kev_date_added":null,"published":"2020-07-14"},{"cvss_score":7.5,"headline":"\"Verify All\" Returns Success Despite Validation Failures in Singularity","id":"CVE-2020-13846","kev_date_added":null,"published":"2020-07-14"},{"cvss_score":7.5,"headline":"Other in n/a","id":"CVE-2020-13847","kev_date_added":null,"published":"2020-07-14"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Insecure directory permissions in Singularity allow attackers to leak information and redirect cloud service operations.","url":"https://insights.sbomify.com/CVE-2019-19724/"}