{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-30274 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-30274 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-30274 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-30274 and fix it if it is affected.\n\nWhat it is: CVE-2022-30274 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-30274 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-30274/ (Markdown: https://insights.sbomify.com/CVE-2022-30274/index.md)","id":"CVE-2022-30274","markdown":"https://insights.sbomify.com/CVE-2022-30274/index.md","name":"CVE-2022-30274","record":{"aliases":["GHSA-pjfq-94vc-mg9w"],"analysis":{"component_type":"ics_ot","fix_type":"no_fix_stated","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Motorola ACE1000 RTU","requires_auth":"none","summary":"Hardcoded TEA keys in ECB mode allow attackers to decrypt stored credentials and bypass authentication on the Motorola ACE1000 RTU.","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":"nvd","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"}],"description":"The Motorola ACE1000 RTU through 2022-05-02 uses ECB encryption unsafely. It can communicate with an XRT LAN-to-radio gateway by means of an embedded client. Credentials for accessing this gateway are stored after being encrypted with the Tiny Encryption Algorithm (TEA) in ECB mode using a hardcoded key. Similarly, the ACE1000 RTU can route MDLC traffic over Extended Command and Management Protocol (XCMP) and Network Layer (XNL) networks via the MDLC driver. Authentication to the XNL port is protected by TEA in ECB mode using a hardcoded key.","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-30274","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":"Hardcoded credentials in n/a","id":"CVE-2022-30275"},"packages":[],"prev":{"headline":"Weak cryptography in n/a","id":"CVE-2022-30273"},"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":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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Hardcoded TEA keys in ECB mode allow attackers to decrypt stored credentials and bypass authentication on the Motorola ACE1000 RTU.","url":"https://insights.sbomify.com/CVE-2022-30274/"}