{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-30320 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-30320 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-30320 is a medium-severity vulnerability in n/a, published on 28 Jul 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-30320 and fix it if it is affected.\n\nWhat it is: CVE-2022-30320 is a medium-severity vulnerability in n/a, published on 28 Jul 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-30320 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-30320/ (Markdown: https://insights.sbomify.com/CVE-2022-30320/index.md)","id":"CVE-2022-30320","markdown":"https://insights.sbomify.com/CVE-2022-30320/index.md","name":"CVE-2022-30320","record":{"aliases":["GHSA-99h8-7hr4-j9f9"],"analysis":{"component_type":"ics_ot","fix_type":"no_fix_stated","impacts":["privilege_escalation","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"SBC PCD controller","requires_auth":"none","summary":"Weak CRC-16 hashing in S-Bus authentication allows attackers to bypass password protection and manipulate controller configuration.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"saia_pg5_controls_suite","vendor":"honeywell"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"}],"description":"Saia Burgess Controls (SBC) PCD through 2022-05-06 uses a Broken or Risky Cryptographic Algorithm. According to FSCT-2022-0063, there is a Saia Burgess Controls (SBC) PCD S-Bus weak credential hashing scheme issue. The affected components are characterized as: S-Bus (5050/UDP) authentication. The potential impact is: Authentication bypass. The Saia Burgess Controls (SBC) PCD controllers utilize the S-Bus protocol (5050/UDP) for a variety of engineering purposes. It is possible to configure a password in order to restrict access to sensitive engineering functionality. Authentication is done by using the S-Bus 'write byte' message to a specific address and supplying a hashed version of the password. The hashing algorithm used is based on CRC-16 and as such not cryptographically secure. An insecure hashing algorithm is used. An attacker capable of passively observing traffic can intercept the hashed credentials and trivially find collisions allowing for authentication without having to bruteforce a keyspace defined by the actual strength of the password. This allows the attacker access to sensitive engineering functionality such as uploading/downloading control logic and manipulating controller configuration.","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":"Weak cryptography in n/a","id":"CVE-2022-30320","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Path traversal in n/a","id":"CVE-2022-30321"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2022-30319"},"products":["n/a"],"published":"2022-07-28","related":[{"cvss_score":8.1,"headline":"Auth bypass in n/a","id":"CVE-2022-30319","kev_date_added":null,"published":"2022-07-28"},{"cvss_score":7.8,"headline":"Honeywell Saia PG5 Controls Suite Directory Traversal Remote Code Execution Vulnerability","id":"CVE-2023-51599","kev_date_added":null,"published":"2024-05-03"},{"cvss_score":7.8,"headline":"Honeywell Saia PG5 Controls Suite CAB File Parsing Directory Traversal Remote Code Execution Vulnerability","id":"CVE-2023-51603","kev_date_added":null,"published":"2024-05-03"},{"cvss_score":5.5,"headline":"Honeywell Saia PG5 Controls Suite XML External Entity Processing Information Disclosure Vulnerability","id":"CVE-2023-51600","kev_date_added":null,"published":"2024-05-03"},{"cvss_score":5.5,"headline":"Honeywell Saia PG5 Controls Suite XML External Entity Processing Information Disclosure Vulnerability","id":"CVE-2023-51601","kev_date_added":null,"published":"2024-05-03"},{"cvss_score":5.5,"headline":"Honeywell Saia PG5 Controls Suite XML External Entity Processing Information Disclosure Vulnerability","id":"CVE-2023-51602","kev_date_added":null,"published":"2024-05-03"},{"cvss_score":5.5,"headline":"Honeywell Saia PG5 Controls Suite XML External Entity Processing Information Disclosure Vulnerability","id":"CVE-2023-51604","kev_date_added":null,"published":"2024-05-03"}],"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":"Weak CRC-16 hashing in S-Bus authentication allows attackers to bypass password protection and manipulate controller configuration.","url":"https://insights.sbomify.com/CVE-2022-30320/"}