{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2022-30262 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-30262 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-30262 is a high-severity vulnerability in n/a, published on 17 Aug 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-2022-30262 and fix it if it is affected.\n\nWhat it is: CVE-2022-30262 is a high-severity vulnerability in n/a, published on 17 Aug 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-2022-30262 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-2022-30262/ (Markdown: https://insights.sbomify.com/CVE-2022-30262/index.md)","id":"CVE-2022-30262","markdown":"https://insights.sbomify.com/CVE-2022-30262/index.md","name":"CVE-2022-30262","record":{"aliases":["GHSA-g3xq-mfm7-v29h"],"analysis":{"component_type":"ics_ot","fix_type":"no_fix_stated","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"RTU firmware","requires_auth":"low_privilege","summary":"Attackers can bypass firmware integrity checks to install malicious firmware on Emerson ControlWave RTUs due to lack of signing.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"controlwave_micro_firmware","vendor":"emerson"},{"product":"controlwave_pac_firmware","vendor":"emerson"}],"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-345","name":"Insufficient Verification of Data Authenticity"}],"description":"The Emerson ControlWave 'Next Generation' RTUs through 2022-05-02 mishandle firmware integrity. They utilize the BSAP-IP protocol to transmit firmware updates. Firmware updates are supplied as CAB archive files containing a binary firmware image. In all cases, firmware images were found to have no authentication (in the form of firmware signing) and only relied on insecure checksums for regular integrity checks.","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-2022-30262","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Path traversal in n/a","id":"CVE-2022-30264"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2022-30260"},"products":["n/a"],"published":"2022-08-17","related":[{"cvss_score":7.5,"headline":"Memory corruption in Emerson ControlWave Micro Process Automation Controller","id":"CVE-2018-5452","kev_date_added":null,"published":"2018-03-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":"Attackers can bypass firmware integrity checks to install malicious firmware on Emerson ControlWave RTUs due to lack of signing.","url":"https://insights.sbomify.com/CVE-2022-30262/"}