Alerton Ascent Control Module FirmwareOperating system · Honeywell

CVE-2022-30244

HIGH · 8.0 CVSS v3.1 Published 2022-07-15
Fix available
A fix is available. Upgrade to after 2022-05-04 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable

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 Ascent Control Module (ACM) through 2022-05-04 allows unauthenticated programming writes from remote users. This enables code to be store 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 · high confidence

The Honeywell Alerton Ascent Control Module (ACM) lacks authentication enforcement for remote programming write operations, allowing unauthenticated attackers to send crafted packets that can modify, inject, or stop control logic running on the controller without detection.

MitigationPrimary mitigations include network segmentation to isolate the control system from untrusted networks and implementing firewall rules to restrict access to authorized endpoints only; coordinate with Honeywell for firmware updates that address the authentication bypass.

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
Alerton Ascent Control Module 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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 Honeywell Alerton Ascent Control Module on the network
    Locate and confirm any Honeywell Alerton Ascent Control Module (ACM) devices on the network by reviewing asset inventories, network scans, or device documentation
    Affected if A Honeywell Alerton Ascent Control Module is present in the environment
  2. Check the ACM firmware version
    Access the device management interface or use the vendor-provided tool to retrieve the installed firmware version, then compare it against the affected range of versions <= 2022-05-04
    Affected if The firmware version is 2022-05-04 or earlier
  3. Verify remote programming interface exposure
    Determine if the remote programming or configuration interface on the ACM is exposed to the network by reviewing firewall rules, access control lists, and network segmentation configurations
    Affected if The remote programming interface is accessible from untrusted networks or unauthorized IP addresses
  4. Inspect authentication configuration for programming operations
    Review the ACM security settings to confirm whether authentication is enforced for remote programming or write operations; check if the device allows unauthenticated write access to control logic
    Affected if Authentication is not enforced or is bypassed for remote programming write operations

The environment is affected if a Honeywell Alerton Ascent Control Module with firmware version 2022-05-04 or earlier has its remote programming interface exposed without proper authentication enforcement.

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

Primary mitigations include network segmentation to isolate the control system from untrusted networks and implementing firewall rules to restrict access to authorized endpoints only; coordinate with Honeywell for firmware updates that address the authentication bypass.

Fix this in Alerton Ascent Control Module Firmware Scoped from the published advisory
  • Consultation10.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
34.0 hours of engineering $6,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-30244 — 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-30244 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