{"answers":{"affected":"It affects 5 products.","exploited":"There is no known exploitation of CVE-2022-30312 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-30312 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-30312 is a medium-severity vulnerability in n/a, published on 7 Sep 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-30312 and fix it if it is affected.\n\nWhat it is: CVE-2022-30312 is a medium-severity vulnerability in n/a, published on 7 Sep 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-30312 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-30312/ (Markdown: https://insights.sbomify.com/CVE-2022-30312/index.md)","id":"CVE-2022-30312","markdown":"https://insights.sbomify.com/CVE-2022-30312/index.md","name":"CVE-2022-30312","record":{"aliases":["GHSA-3pvh-38hr-8x7c"],"analysis":{"component_type":"ics_ot","fix_type":"no_fix_stated","impacts":["data_read","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Building automation controller","requires_auth":"none","summary":"Attackers can intercept cleartext credentials in Trend Controls IC protocol traffic to gain unauthorized access and manipulate building automation systems.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"trend_iq411_firmware","vendor":"honeywell"},{"product":"trend_iq412_firmware","vendor":"honeywell"},{"product":"trend_iq422_firmware","vendor":"honeywell"},{"product":"trend_iq4e_firmware","vendor":"honeywell"},{"product":"trend_iq4nc_firmware","vendor":"honeywell"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-319","name":"Cleartext Transmission of Sensitive Information"}],"description":"The Trend Controls IC protocol through 2022-05-06 allows Cleartext Transmission of Sensitive Information. According to FSCT-2022-0050, there is a Trend Controls Inter-Controller (IC) protocol cleartext transmission of credentials issue. The affected components are characterized as: Inter-Controller (IC) protocol (57612/UDP). The potential impact is: Compromise of credentials. Several Trend Controls building automation controllers utilize the Inter-Controller (IC) protocol in for information exchange and automation purposes. This protocol offers authentication in the form of a 4-digit PIN in order to protect access to sensitive operations like strategy uploads and downloads as well as optional 0-30 character username and password protection for web page access protection. Both the PIN and usernames and passwords are transmitted in cleartext, allowing an attacker with passive interception capabilities to obtain these credentials. Credentials are transmitted in cleartext. An attacker who obtains Trend IC credentials can carry out sensitive engineering actions such as manipulating controller strategy or configuration settings. If the credentials in question are (re)used for other applications, their compromise could potentially facilitate lateral movement.","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":"Information disclosure in n/a","id":"CVE-2022-30312","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Missing authorization in n/a","id":"CVE-2022-30313"},"packages":[],"prev":{"headline":"FESTO: CECC-X-M1 and Servo Press Kit YJKP OS Command Injection vulnerability","id":"CVE-2022-30311"},"products":["n/a"],"published":"2022-09-07","related":[],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-06-17","vendors":["n/a"]},"summary":"Attackers can intercept cleartext credentials in Trend Controls IC protocol traffic to gain unauthorized access and manipulate building automation systems.","url":"https://insights.sbomify.com/CVE-2022-30312/"}