{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-33220 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-33220 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-33220 is a high-severity vulnerability in n/a, published on 7 Jul 2021. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-33220 and fix it if it is affected.\n\nWhat it is: CVE-2021-33220 is a high-severity vulnerability in n/a, published on 7 Jul 2021. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-33220 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-33220/ (Markdown: https://insights.sbomify.com/CVE-2021-33220/index.md)","id":"CVE-2021-33220","markdown":"https://insights.sbomify.com/CVE-2021-33220/index.md","name":"CVE-2021-33220","record":{"aliases":["GHSA-2qqr-7rg8-6qmh"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Ruckus IoT Controller","requires_auth":"low_privilege","summary":"Hard-coded API keys in the Ruckus IoT Controller allow attackers to bypass authentication and access sensitive data.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ruckus_iot_controller","vendor":"commscope"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"An issue was discovered in CommScope Ruckus IoT Controller 1.7.1.0 and earlier. Hard-coded API Keys exist.","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":"Hardcoded credentials in n/a","id":"CVE-2021-33220","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Missing authorization in n/a","id":"CVE-2021-33221"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2021-33219"},"products":["n/a"],"published":"2021-07-07","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2021-33216","kev_date_added":null,"published":"2021-07-07"},{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2021-33218","kev_date_added":null,"published":"2021-07-07"},{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2021-33219","kev_date_added":null,"published":"2021-07-07"},{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2021-33221","kev_date_added":null,"published":"2021-07-07"},{"cvss_score":8.8,"headline":"Path traversal in n/a","id":"CVE-2021-33217","kev_date_added":null,"published":"2021-07-07"},{"cvss_score":4.3,"headline":"Path traversal in n/a","id":"CVE-2021-33215","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-08-03","vendors":["n/a"]},"summary":"Hard-coded API keys in the Ruckus IoT Controller allow attackers to bypass authentication and access sensitive data.","url":"https://insights.sbomify.com/CVE-2021-33220/"}