{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-30271 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-30271 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-30271 is a critical vulnerability in n/a, published on 26 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-30271 and fix it if it is affected.\n\nWhat it is: CVE-2022-30271 is a critical vulnerability in n/a, published on 26 Jul 2022. 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-2022-30271 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-30271/ (Markdown: https://insights.sbomify.com/CVE-2022-30271/index.md)","id":"CVE-2022-30271","markdown":"https://insights.sbomify.com/CVE-2022-30271/index.md","name":"CVE-2022-30271","record":{"aliases":["GHSA-59rw-g46v-6c42"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["account_takeover","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Motorola ACE1000 RTU","requires_auth":"none","summary":"Attackers can use a hardcoded SSH private key to gain unauthorized access to Motorola ACE1000 RTUs, potentially leading to full system compromise.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ace1000_firmware","vendor":"motorola"}],"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-798","name":"Use of Hard-coded Credentials"},{"id":"CWE-259","name":"Use of Hard-coded Password"}],"description":"The Motorola ACE1000 RTU through 2022-05-02 ships with a hardcoded SSH private key and initialization scripts (such as /etc/init.d/sshd_service) only generate a new key if no private-key file exists. Thus, this hardcoded key is likely to be used by default.","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":"Hardcoded credentials in n/a","id":"CVE-2022-30271","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2022-30272"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2022-30270"},"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-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"},{"cvss_score":7.2,"headline":"Security feature bypass in n/a","id":"CVE-2022-30272","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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Attackers can use a hardcoded SSH private key to gain unauthorized access to Motorola ACE1000 RTUs, potentially leading to full system compromise.","url":"https://insights.sbomify.com/CVE-2022-30271/"}