{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-11400 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-11400 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-11400 is a medium-severity vulnerability in n/a, published on 20 Nov 2017. 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-2017-11400 and fix it if it is affected.\n\nWhat it is: CVE-2017-11400 is a medium-severity vulnerability in n/a, published on 20 Nov 2017. 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-2017-11400 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-2017-11400/ (Markdown: https://insights.sbomify.com/CVE-2017-11400/index.md)","id":"CVE-2017-11400","markdown":"https://insights.sbomify.com/CVE-2017-11400/index.md","name":"CVE-2017-11400","record":{"aliases":["GHSA-mrc4-5458-65m9"],"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 security appliance","requires_auth":"none","summary":"Local attackers can bypass firmware signature checks to install malicious kernel and file system updates on Belden Hirschmann Tofino Xenon appliances.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"tofino_xenon_security_appliance_firmware","vendor":"belden"}],"cvss":{"score":6.8,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"An issue has been discovered on the Belden Hirschmann Tofino Xenon Security Appliance before 03.2.00. An incomplete firmware signature allows a local attacker to upgrade the equipment (kernel, file system) with unsigned, attacker-controlled, data. This occurs because the appliance_config file is signed but the .tar.sec file is unsigned.","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-2017-11400","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2017-11401"},"packages":[],"prev":{"headline":"Integer overflow in n/a","id":"CVE-2017-11399"},"products":["n/a"],"published":"2017-11-20","related":[{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2017-11401","kev_date_added":null,"published":"2017-11-20"},{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2017-11402","kev_date_added":null,"published":"2017-11-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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Local attackers can bypass firmware signature checks to install malicious kernel and file system updates on Belden Hirschmann Tofino Xenon appliances.","url":"https://insights.sbomify.com/CVE-2017-11400/"}