dbcve.org
Out-of-bounds ReadWeakness · CWE-125

CVE-2024-54090

MEDIUM · 5.9 CVSS v3.1 Published 2025-02-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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
A vulnerability has been identified in APOGEE PXC Series (BACnet) (All versions), APOGEE PXC Series (P2 Ethernet) (All versions), TALON TC Series (BACnet) (All versions). Affected devices contain an out-of-bounds read in the memory dump function. This could allow an attacker with Medium (MED) or higher privileges to cause the device to enter an insecure cold start state.

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

An out-of-bounds read vulnerability exists in the memory dump function of APOGEE PXC Series (BACnet/P2 Ethernet) and TALON TC Series building automation controllers. This allows authenticated attackers with Medium or higher privileges to read unintended memory regions, potentially causing the device to enter an insecure cold start state.

MitigationSince all versions are affected, implement network segmentation to isolate BACnet devices from untrusted networks, enforce strict access control limiting administrative privileges, and monitor for indicators of exploitation. Contact Schneider Electric for available firmware updates or patches.

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

CVSS:3.1/AV:N/AC:H/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. Identify APOGEE PXC or TALON TC controllers on the network
    Use network scanning tools (e.g., nmap, BACnet discovery tools) to identify BACnet devices. Check device inventory or management interfaces for model numbers PXC Series or TC Series.
    Affected if APOGEE PXC Series or TALON TC Series building automation controllers are present on the network.
  2. Verify BACnet/P2 Ethernet interface is enabled
    Access the controller web interface or management console and check the network configuration for BACnet/P2 Ethernet protocol settings. Confirm the interface is active and listening on BACnet ports (UDP 47808).
    Affected if The BACnet/P2 Ethernet interface is enabled and exposed on the network.
  3. Confirm authentication and privilege level configuration
    Check user account settings in the controller administration panel. Identify accounts with Medium or higher privilege levels (such as Administrator, Operator, or equivalent).
    Affected if User accounts with Medium or higher privileges exist on the device.
  4. Review network exposure of the controller
    Examine firewall rules, VLAN segmentation, and access control lists to determine if the BACnet management interface is accessible from untrusted networks or the internet.
    Affected if The controller's BACnet interface is accessible from untrusted network segments or directly from the internet.
  5. Check for memory dump function accessibility
    Locate the memory dump or diagnostic function in the controller web UI or management CLI. Verify if this feature is accessible to authenticated users with Medium privileges or higher.
    Affected if The memory dump feature is accessible to authenticated users without additional restrictions beyond the Medium privilege requirement.

If APOGEE PXC Series or TALON TC Series controllers with BACnet/P2 Ethernet enabled are present and accessible to authenticated users with Medium or higher privileges, the environment is affected by this vulnerability.

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

Since all versions are affected, implement network segmentation to isolate BACnet devices from untrusted networks, enforce strict access control limiting administrative privileges, and monitor for indicators of exploitation. Contact Schneider Electric for available firmware updates or patches.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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