dbcve.org
Niagara FrameworkApplication · Honeywell

CVE-2024-1309

HIGH · 7.5 CVSS v3.1 Published 2024-02-13
Fix available
A fix is available. Upgrade to 3.8.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable 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
Uncontrolled Resource Consumption vulnerability in Honeywell Niagara Framework on Windows, Linux, QNX allows Content Spoofing.This issue affects Niagara Framework: before Niagara AX 3.8.1, before Niagara 4.1.

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

Uncontrolled Resource Consumption vulnerability in Honeywell Niagara Framework allows Content Spoofing. The specific nature of the resource consumption is not detailed, but it enables an attacker to manipulate content displayed to users. The vulnerability affects Niagara Framework versions before Niagara AX 3.8.1 and before Niagara 4.1 on Windows, Linux, and QNX platforms.

MitigationUpgrade Niagara Framework to version AX 3.8.1 or 4.1 or later to remediate this vulnerability.

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
Niagara FrameworkApplication
Affected:< 3.8.1

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Confirm Niagara Framework installation
    Locate Niagara installation directories or identify Niagara-related services running on the system. Check common installation paths or use system utilities to list installed software packages.
    Affected if Niagara Framework is present on the system
  2. Identify the Niagara product line
    Determine whether the installation is Niagara AX (legacy) or Niagara 4 by checking the product name in the version information, about dialog, or installation metadata.
    Affected if The product is either Niagara AX or Niagara 4
  3. Check the installed version number
    Retrieve the exact version number through the system's version reporting mechanism, such as the Niagara about screen, version command, or version configuration file. Compare the installed version against the affected ranges: any version before 3.8.1 for Niagara AX, or any version before 4.1 for Niagara 4.
    Affected if The installed version is below 3.8.1 for Niagara AX, or below 4.1 for Niagara 4
  4. Verify the operating system platform
    Identify the operating system where Niagara is running. This vulnerability affects Windows, Linux, and QNX platforms.
    Affected if The system runs on Windows, Linux, or QNX and meets the version conditions above

A user is affected if Niagara Framework is installed and the running version is below AX 3.8.1 or below 4.1 on Windows, Linux, or QNX platforms.

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.

dbcve · scoped
Upgrade available Upgrade to 3.8.1 or later
Fixed in 3.8.1
Interim mitigation

Upgrade Niagara Framework to version AX 3.8.1 or 4.1 or later to remediate this vulnerability.

Recommended fix Moderate confidence

Niagara AX 3.8.1 or later, or Niagara 4.1 or later

  1. Identify the current version of Honeywell Niagara Framework installed in your environment
  2. Determine if the current version is Niagara AX or Niagara 4.x by checking the framework version
  3. If running Niagara AX version < 3.8.1, upgrade to Niagara AX version 3.8.1 or later
  4. If running Niagara 4.x version < 4.1, upgrade to Niagara 4.1 or later
  5. After upgrade, verify the framework is operational and all services start correctly
  6. Review application logs to confirm no resource consumption issues remain
Caveat Review release notes for any breaking changes between your current version and the target upgrade version; test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Niagara Framework Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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