{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-32520 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-32520 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-32520 is a critical vulnerability in QSAN Storage Manager, published on 7 Jul 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-32520 and fix it if it is affected.\n\nWhat it is: CVE-2021-32520 is a critical vulnerability in QSAN Storage Manager, published on 7 Jul 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-32520 in the wild and no public exploit code.\n\nAffected product: QSAN Storage Manager. 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-32520/ (Markdown: https://insights.sbomify.com/CVE-2021-32520/index.md)","id":"CVE-2021-32520","markdown":"https://insights.sbomify.com/CVE-2021-32520/index.md","name":"CVE-2021-32520","record":{"aliases":["GHSA-64pf-575c-cqw5"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"QSAN Storage Manager","requires_auth":"none","summary":"Attackers can obtain user credentials and permissions due to a hard-coded cryptographic key in QSAN Storage Manager.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"twcert","cpe":[{"product":"storage_manager","vendor":"qsan"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","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-798","name":"Use of Hard-coded Credentials"},{"id":"CWE-321","name":"Use of Hard-coded Cryptographic Key"}],"description":"Use of hard-coded cryptographic key vulnerability in QSAN Storage Manager allows attackers to obtain users’ credentials and related permissions. Suggest contacting with QSAN and refer to recommendations in QSAN Document.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"QSAN Storage Manager - Use of Hard-coded Cryptographic Key","id":"CVE-2021-32520","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"QSAN Storage Manager, XEVO, SANOS - Use of Hard-coded Password","id":"CVE-2021-32521"},"packages":[],"prev":{"headline":"QSAN Storage Manager, XEVO, SANOS - Use of Password Hash With Insufficient Computational Effort","id":"CVE-2021-32519"},"products":["Storage Manager"],"published":"2021-07-07","related":[{"cvss_score":9.8,"headline":"QSAN Storage Manager - Command Injection Following via QuickInstall function","id":"CVE-2021-32512","kev_date_added":null,"published":"2021-07-07"},{"cvss_score":9.8,"headline":"QSAN Storage Manager - Command Injection Following via QsanTorture function","id":"CVE-2021-32513","kev_date_added":null,"published":"2021-07-07"},{"cvss_score":9.1,"headline":"QSAN Storage Manager - Improper Authorization","id":"CVE-2021-32523","kev_date_added":null,"published":"2021-07-07"},{"cvss_score":9.1,"headline":"QSAN Storage Manager - Command Injection-3","id":"CVE-2021-32524","kev_date_added":null,"published":"2021-07-07"},{"cvss_score":9.1,"headline":"QSAN Storage Manager - Use of Hard-coded Password-2","id":"CVE-2021-32525","kev_date_added":null,"published":"2021-07-07"},{"cvss_score":7.5,"headline":"QSAN Storage Manager - Improper Access Control Following via FirwareUpgrade function","id":"CVE-2021-32514","kev_date_added":null,"published":"2021-07-07"}],"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-09-17","vendors":["QSAN"]},"summary":"Attackers can obtain user credentials and permissions due to a hard-coded cryptographic key in QSAN Storage Manager.","url":"https://insights.sbomify.com/CVE-2021-32520/"}