CVE-2025-24510
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 · uneditedA vulnerability has been identified in MS/TP Point Pickup Module (All versions). Affected devices improperly handle specific incoming BACnet MSTP messages. This could allow an attacker residing in the same BACnet network to send a specially crafted MSTP message that results in a denial of service condition of the targeted device. A power cycle is required to restore the device's normal operation.
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 confidenceThe MS/TP Point Pickup Module has a vulnerability in its BACnet MSTP message parsing logic. Specially crafted MSTP frames can trigger a fault condition causing the device to cease normal operation. The device requires a power cycle to recover, indicating a potential memory corruption or unhandled exception state.
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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/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 checksWork through these to decide whether this CVE applies to you.
-
Identify BACnet MS/TP deploymentInventory systems using BACnet MS/TP protocol. Look for Point Pickup Modules or similar devices in network documentation or through BACnet device discovery scans.Affected if BACnet MS/TP devices are present in the environment
-
Verify MS/TP Point Pickup Module is in useCheck device inventory or scan for BACnet devices. Identify if the device is specifically an MS/TP Point Pickup Module that handles MSTP frame parsing.Affected if An MS/TP Point Pickup Module is present and configured to process MSTP traffic
-
Confirm MSTP message parsing is enabledReview the device configuration to verify that MSTP frame parsing is active and the device accepts incoming MSTP frames from the network.Affected if MSTP parsing is enabled and the device is exposed to network MSTP traffic
-
Check for crash or fault events requiring power cycleReview system logs, device event logs, or network monitoring systems for incidents of unexplained device resets or faults. Correlate with any MSTP traffic activity.Affected if Devices exhibit unexpected fault conditions requiring power cycle to recover, especially after MSTP traffic events
-
Monitor for anomalous MSTP framesUse BACnet protocol analyzer or network monitoring tools to inspect MSTP traffic for malformed or specially crafted frames that could trigger the vulnerability.Affected if Malformed MSTP frames are detected or device shows instability following receipt of unusual MSTP traffic
Environment is affected if an MS/TP Point Pickup Module with enabled MSTP message parsing is exposed to untrusted BACnet MSTP network traffic, potentially causing fault conditions that require a power cycle to recover.
Generated from the published advisory. Verify against your own configuration.
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 dataIsolate BACnet MSTP segments from untrusted networks and filter unauthorized MSTP traffic at network boundaries. Apply vendor firmware updates when available and implement network monitoring to detect anomalous MSTP frames.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-24510 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-24510 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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