dbcve.org
Trend Iq412 FirmwareOperating system · Honeywell

CVE-2022-30312

MEDIUM · 6.5 CVSS v3.1 Published 2022-09-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Trend Controls Inter-Controller (IC) protocol transmits 4-digit PIN and optional username/password credentials in cleartext over UDP port 57612, allowing passive network observers to intercept authentication credentials and gain unauthorized access to controller operations.

MitigationImplement network segmentation or VPN tunneling to encapsulate IC protocol traffic; consider deploying Trend Controls hardware/firmware updates if available that support encrypted authentication.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Trend Iq412 FirmwareOperating system
Affected:all versions
Trend Iq411 FirmwareOperating system
Affected:all versions
Trend Iq422 FirmwareOperating system
Affected:all versions
Trend Iq4nc FirmwareOperating system
Affected:all versions
Trend Iq4e FirmwareOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Trend IC protocol listeners
    Scan the network for devices listening on UDP port 57612 using a port scanner (e.g., nmap -sU -p 57612 <target>)
    Affected if UDP port 57612 is open and responding on any device on the network
  2. Confirm Trend device firmware
    Access the device management interface or check the device label to identify the exact model and firmware version (Iq412, Iq411, Iq422, Iq4nc, or Iq4e)
    Affected if The device runs any of the listed Honeywell Trend firmware variants (Iq412, Iq411, Iq422, Iq4nc, Iq4e)
  3. Verify IC protocol is enabled
    Check the device configuration settings for Inter-Controller protocol settings; look for IC protocol enable/disable options in the Trend device management interface
    Affected if The IC protocol feature is enabled on the device
  4. Inspect network traffic for cleartext credentials
    Capture UDP traffic on port 57612 using a packet sniffer (e.g., tcpdump or Wireshark) and analyze the payload for plaintext PIN, username, or password strings
    Affected if Captured UDP packets on port 57612 contain readable PIN codes or authentication credentials in the payload

You are affected if you have any Honeywell Trend Iq412, Iq411, Iq422, Iq4nc, or Iq4e devices with the IC protocol enabled and UDP port 57612 exposed on your network, where cleartext credentials can be observed in captured traffic.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement network segmentation or VPN tunneling to encapsulate IC protocol traffic; consider deploying Trend Controls hardware/firmware updates if available that support encrypted authentication.

Fix this in Trend Iq412 Firmware Scoped from the published advisory
  • Consultation12.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
60.0 hours of engineering $10,560
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $16,896.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-30312 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-30312 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data