dbcve.org
Incorrect Permission AssignmentWeakness · CWE-732

CVE-2024-41974

HIGH · 7.1 CVSS v3.1 Published 2024-11-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
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
A low privileged remote attacker may modify the BACNet service properties due to incorrect permission assignment for critical resources which may lead to a DoS limited to BACNet communication.

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

This is an incorrect permission assignment vulnerability in BACNet (Building Automation and Control Networks) services where a low-privileged remote attacker can modify BACNet service properties due to overly permissive access controls on critical resources. The vulnerability allows the attacker to alter service configuration, resulting in denial of service specifically affecting BACNet communication.

MitigationReview and restrict permission assignments on BACNet service properties to enforce least-privilege access controls, ensuring only authorized administrators can modify critical service configurations.

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

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
None
Integrity
Low
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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 if BACNet services are running
    Review running services or daemons related to Building Automation and Control Networks (BACNet). Check for processes with names containing 'bacnet', 'bacnet-server', or similar. Use commands like 'systemctl list-units --type=service' or 'ps aux | grep -i bacnet' to enumerate active BACNet processes.
    Affected if BACNet services are actively running and exposing BACNet protocol ports (typically UDP port 47808) on the network.
  2. Locate BACNet configuration files
    Search for BACNet configuration files in common locations: /etc/bacnet/, /opt/bacnet/, or within the application's config directory. Look for files named bacnet.conf, bacnet.xml, config.ini, or similar that define service properties and access controls.
    Affected if BACNet configuration files exist and contain access control or permission settings for service properties.
  3. Review access control permissions on BACNet service properties
    Examine the identified BACNet configuration files for entries controlling who can modify service properties. Look for sections labeled 'access-control', 'permissions', 'authorization', 'write-access', or 'property-modification'. Check if these settings allow anonymous, guest, or low-privilege accounts to alter critical service configurations.
    Affected if The configuration grants write or modify access to unauthenticated, anonymous, or low-privilege users on critical BACNet service properties.
  4. Verify user privilege levels for BACNet service modification
    If using an integrated Building Management System (BMS) or SCADA platform running BACNet, review user role definitions and privilege assignments. Check whether user roles below 'administrator' or 'operator' level have been granted permissions to modify BACNet service settings, network parameters, or device objects.
    Affected if Non-administrator user accounts or groups are assigned permissions to modify BACNet service configuration properties.
  5. Test write access to BACNet service properties
    Using a BACNet client tool (such as Yabe, BACnet Scanner, or similar), attempt to write to critical service properties (such as network configuration, device identification, or communication parameters) using a low-privilege or anonymous account. Observe whether the write operation succeeds.
    Affected if A low-privilege or unauthenticated BACNet client can successfully modify service properties without rejection or authentication failure.

Your environment is affected if BACNet services are running and access control configurations permit low-privilege or anonymous users to modify service properties, which could lead to denial of BACNet communication.

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

Review and restrict permission assignments on BACNet service properties to enforce least-privilege access controls, ensuring only authorized administrators can modify critical service configurations.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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