{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-30272 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-30272 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-30272 is a high-severity vulnerability in n/a, published on 26 Jul 2022. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-30272 and fix it if it is affected.\n\nWhat it is: CVE-2022-30272 is a high-severity vulnerability in n/a, published on 26 Jul 2022. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-30272 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-30272/ (Markdown: https://insights.sbomify.com/CVE-2022-30272/index.md)","id":"CVE-2022-30272","markdown":"https://insights.sbomify.com/CVE-2022-30272/index.md","name":"CVE-2022-30272","record":{"aliases":["GHSA-23v4-qfpm-c2cx"],"analysis":{"component_type":"ics_ot","fix_type":"no_fix_stated","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Motorola ACE1000 RTU","requires_auth":"high_privilege","summary":"Attackers can install malicious firmware on Motorola ACE1000 RTUs because updates lack cryptographic signing, allowing arbitrary code execution.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ace1000_firmware","vendor":"motorola"}],"cvss":{"score":7.2,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:H/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 Motorola ACE1000 RTU through 2022-05-02 mishandles firmware integrity. It utilizes either the STS software suite or ACE1000 Easy Configurator for performing firmware updates. In case of the Easy Configurator, firmware updates are performed through access to the Web UI where file system, kernel, package, bundle, or application images can be installed. Firmware updates for the Front End Processor (FEP) module are performed via access to the SSH interface (22/TCP), where a .hex file image is transferred and a bootloader script invoked. File system, kernel, package, and bundle updates are supplied as RPM (RPM Package Manager) files while FEP updates are supplied as S-rec files. 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-30272","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":"Weak cryptography in n/a","id":"CVE-2022-30273"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2022-30271"},"products":["n/a"],"published":"2022-07-26","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2022-30270","kev_date_added":null,"published":"2022-07-26"},{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2022-30271","kev_date_added":null,"published":"2022-07-26"},{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2022-30274","kev_date_added":null,"published":"2022-07-26"},{"cvss_score":8.8,"headline":"Security feature bypass in n/a","id":"CVE-2022-30269","kev_date_added":null,"published":"2022-07-26"}],"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 install malicious firmware on Motorola ACE1000 RTUs because updates lack cryptographic signing, allowing arbitrary code execution.","url":"https://insights.sbomify.com/CVE-2022-30272/"}