{"answers":{"affected":"It affects 14 products.","exploited":"There is no known exploitation of CVE-2020-22653 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-22653 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-22653 is a critical vulnerability in n/a, published on 20 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-22653 and fix it if it is affected.\n\nWhat it is: CVE-2020-22653 is a critical vulnerability in n/a, published on 20 Jan 2023. 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-2020-22653 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-2020-22653/ (Markdown: https://insights.sbomify.com/CVE-2020-22653/index.md)","id":"CVE-2020-22653","markdown":"https://insights.sbomify.com/CVE-2020-22653/index.md","name":"CVE-2020-22653","record":{"aliases":["GHSA-xr9x-fhcv-6qm7"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Ruckus wireless infrastructure","requires_auth":"none","summary":"Attackers can bypass image signature verification to inject unauthorized firmware, potentially leading to code execution on Ruckus wireless devices.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"r310_firmware","vendor":"ruckuswireless"},{"product":"r500_firmware","vendor":"ruckuswireless"},{"product":"r600_firmware","vendor":"ruckuswireless"},{"product":"scg200_firmware","vendor":"ruckuswireless"},{"product":"sz-100_firmware","vendor":"ruckuswireless"},{"product":"sz-300_firmware","vendor":"ruckuswireless"},{"product":"t300_firmware","vendor":"ruckuswireless"},{"product":"t301n_firmware","vendor":"ruckuswireless"},{"product":"t301s_firmware","vendor":"ruckuswireless"},{"product":"vsz_firmware","vendor":"ruckuswireless"},{"product":"zonedirector_1100_firmware","vendor":"ruckuswireless"},{"product":"zonedirector_1200_firmware","vendor":"ruckuswireless"},{"product":"zonedirector_3000_firmware","vendor":"ruckuswireless"},{"product":"zonedirector_5000_firmware","vendor":"ruckuswireless"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","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-347","name":"Improper Verification of Cryptographic Signature"}],"description":"In Ruckus R310 10.5.1.0.199, Ruckus R500 10.5.1.0.199, Ruckus R600 10.5.1.0.199, Ruckus T300 10.5.1.0.199, Ruckus T301n 10.5.1.0.199, Ruckus T301s 10.5.1.0.199, SmartCell Gateway 200 (SCG200) before 3.6.2.0.795, SmartZone 100 (SZ-100) before 3.6.2.0.795, SmartZone 300 (SZ300) before 3.6.2.0.795, Virtual SmartZone (vSZ) before 3.6.2.0.795, ZoneDirector 1100 9.10.2.0.130, ZoneDirector 1200 10.2.1.0.218, ZoneDirector 3000 10.2.1.0.218, ZoneDirector 5000 10.0.1.0.151, a vulnerability allows attackers to exploit the official image signature to force injection unauthorized image signature.","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":"Security feature bypass in n/a","id":"CVE-2020-22653","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2020-22654"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2020-22650"},"products":["n/a"],"published":"2023-01-20","related":[{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2020-22654","kev_date_added":null,"published":"2023-01-20"},{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2020-22658","kev_date_added":null,"published":"2023-01-20"},{"cvss_score":9.1,"headline":"Auth bypass in n/a","id":"CVE-2020-22657","kev_date_added":null,"published":"2023-01-20"},{"cvss_score":7.5,"headline":"Missing authorization in n/a","id":"CVE-2020-22655","kev_date_added":null,"published":"2023-01-20"},{"cvss_score":7.5,"headline":"Security feature bypass in n/a","id":"CVE-2020-22656","kev_date_added":null,"published":"2023-01-20"},{"cvss_score":7.5,"headline":"Security feature bypass in n/a","id":"CVE-2020-22659","kev_date_added":null,"published":"2023-01-20"}],"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-03","vendors":["n/a"]},"summary":"Attackers can bypass image signature verification to inject unauthorized firmware, potentially leading to code execution on Ruckus wireless devices.","url":"https://insights.sbomify.com/CVE-2020-22653/"}