{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2021-33622 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-33622 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-33622 is a critical vulnerability in n/a, published on 15 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-33622 and fix it if it is affected.\n\nWhat it is: CVE-2021-33622 is a critical vulnerability in n/a, published on 15 Jun 2021. 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-2021-33622 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2021-33622/ (Markdown: https://insights.sbomify.com/CVE-2021-33622/index.md)","id":"CVE-2021-33622","markdown":"https://insights.sbomify.com/CVE-2021-33622/index.md","name":"CVE-2021-33622","record":{"aliases":["GHSA-cq54-mjwx-5pjw","UBUNTU-CVE-2021-33622"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"Singularity container runtime","requires_auth":"none","summary":"Singularity container runtime fails to check function return values, potentially leading to undefined behavior or security bypasses.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"singularity","vendor":"sylabs"},{"product":"singularitypro","vendor":"sylabs"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-754","name":"Improper Check for Unusual or Exceptional Conditions"}],"description":"Sylabs Singularity 3.5.x and 3.6.x, and SingularityPRO before 3.5-8, has an Incorrect Check of a Function's Return Value.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Other in n/a","id":"CVE-2021-33622","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Uncontrolled Resource Consumption in trim-newlines","id":"CVE-2021-33623"},"packages":[],"prev":{"headline":"HTTP response splitting in CGI","id":"CVE-2021-33621"},"products":["n/a"],"published":"2021-06-15","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":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"},{"cvss_score":7.5,"headline":"Singularity insecure permissions","id":"CVE-2019-19724","kev_date_added":null,"published":"2019-12-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-03","vendors":["n/a"]},"summary":"Singularity container runtime fails to check function return values, potentially leading to undefined behavior or security bypasses.","url":"https://insights.sbomify.com/CVE-2021-33622/"}