{"answers":{"affected":"It affects 13 products.","exploited":"There is no known exploitation of CVE-2021-30066 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-30066 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-30066 is a medium-severity vulnerability in n/a, published on 3 Apr 2022. 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-30066 and fix it if it is affected.\n\nWhat it is: CVE-2021-30066 is a medium-severity vulnerability in n/a, published on 3 Apr 2022. 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-30066 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-30066/ (Markdown: https://insights.sbomify.com/CVE-2021-30066/index.md)","id":"CVE-2021-30066","markdown":"https://insights.sbomify.com/CVE-2021-30066/index.md","name":"CVE-2021-30066","record":{"aliases":["GHSA-j2pq-xrmc-f4r4"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Industrial Firewall","requires_auth":"none","summary":"Attackers can bypass firmware signature verification to load arbitrary firmware on Schneider Electric and Belden Tofino firewalls, enabling code execution.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"eagle_20_tofino_943_987-501-tx\\/tx_firmware","vendor":"belden"},{"product":"eagle_20_tofino_943_987-502_-tx\\/mm_firmware","vendor":"belden"},{"product":"eagle_20_tofino_943_987-504-mm\\/tx_firmware","vendor":"belden"},{"product":"eagle_20_tofino_943_987-505-mm\\/mm_firmware","vendor":"belden"},{"product":"tofino_argon_fa-tsa-100-tx\\/tx_firmware","vendor":"belden"},{"product":"tofino_argon_fa-tsa-220-mm\\/mm_firmware","vendor":"belden"},{"product":"tofino_argon_fa-tsa-220-mm\\/tx_firmware","vendor":"belden"},{"product":"tofino_argon_fa-tsa-220-tx\\/mm_firmware","vendor":"belden"},{"product":"tofino_argon_fa-tsa-220-tx\\/tx_firmware","vendor":"belden"},{"product":"tofino_xenon_security_appliance_firmware","vendor":"belden"},{"product":"tcsefea23f3f20_firmware","vendor":"schneider-electric"},{"product":"tcsefea23f3f21_firmware","vendor":"schneider-electric"},{"product":"tcsefea23f3f22_firmware","vendor":"schneider-electric"}],"cvss":{"score":6.8,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:P/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":"On Schneider Electric ConneXium Tofino Firewall TCSEFEA23F3F22 before 03.23, TCSEFEA23F3F20/21, and Belden Tofino Xenon Security Appliance, an arbitrary firmware image can be loaded because firmware signature verification (for a USB stick) can be bypassed. NOTE: this issue exists because of an incomplete fix of CVE-2017-11400.","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-2021-30066","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Command injection in n/a","id":"CVE-2021-30070"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2021-30065"},"products":["n/a"],"published":"2022-04-03","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2021-30064","kev_date_added":null,"published":"2022-04-03"},{"cvss_score":7.5,"headline":"Security feature bypass in n/a","id":"CVE-2021-30062","kev_date_added":null,"published":"2022-04-03"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2021-30063","kev_date_added":null,"published":"2022-04-03"},{"cvss_score":7.5,"headline":"Security feature bypass in n/a","id":"CVE-2021-30065","kev_date_added":null,"published":"2022-04-03"},{"cvss_score":6.8,"headline":"Code injection in n/a","id":"CVE-2021-30061","kev_date_added":null,"published":"2022-04-03"}],"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":"Attackers can bypass firmware signature verification to load arbitrary firmware on Schneider Electric and Belden Tofino firewalls, enabling code execution.","url":"https://insights.sbomify.com/CVE-2021-30066/"}