Alterton Visual Logic FirmwareOperating system · Honeywell

CVE-2022-30243

HIGH · 8.8 CVSS v3.1 Published 2022-07-15
Fix available
A fix is available. Upgrade to after 2022-05-04 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Honeywell Alerton Visual Logic through 2022-05-04 allows unauthenticated programming writes from remote users. This enables code to be stored on the controller and then run without verification. A user with malicious intent can send a crafted packet to change and/or stop the program without the knowledge of other users, altering the controller's function. After the programming change, the program needs to be overwritten in order for the controller to restore its original operational function.

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 · moderate confidence

Honeywell Alerton Visual Logic through early May 2022 lacks authentication for programming write operations, allowing remote attackers to send crafted packets that modify or stop controller programs without verification. This enables malicious code injection directly into building automation controllers, with recovery requiring manual program overwrite.

MitigationUpdate Visual Logic to a version after 2022-05-04 that includes authentication enforcement; if no patched version exists, implement network segmentation to restrict remote access to controllers and disable external programming interfaces.

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
Alterton Visual Logic FirmwareOperating system
Affected:<= 2022-05-04

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 Visual Logic firmware version
    Access the controller management interface or use the vendor's configuration software to retrieve the installed firmware version. Compare this date to the 2022-05-04 threshold.
    Affected if The firmware version date is on or before 2022-05-04.
  2. Verify remote programming interface exposure
    Review network configuration to determine if the controller's programming port (typically port 5000/TCP or vendor-specific) is accessible from untrusted networks or the internet.
    Affected if The programming interface is reachable from networks outside the trusted building automation network segment.
  3. Confirm authentication enforcement on write operations
    Attempt a test write operation through the programming interface using the vendor tools while operating as an unauthenticated user, or review security logs for unauthenticated write attempts.
    Affected if Write operations complete or are accepted without requiring valid authentication credentials.
  4. Review controller program integrity
    Use the Visual Logic programming software to list and compare the currently loaded logic programs against known-good backups or baseline configurations.
    Affected if Programs have been modified, contain unexpected logic, or differ from the expected baseline without authorized change documentation.

You are affected if the Visual Logic firmware version is dated 2022-05-04 or earlier AND the programming interface is accessible remotely without requiring authentication.

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
Upgrade available Upgrade to a release after 2022-05-04
Interim mitigation

Update Visual Logic to a version after 2022-05-04 that includes authentication enforcement; if no patched version exists, implement network segmentation to restrict remote access to controllers and disable external programming interfaces.

Fix this in Alterton Visual Logic Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-30243 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