CVE-2025-2403
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 denial-of-service vulnerability due to improper prioritization of network traffic over protection mechanism exists in Relion 670/650 and SAM600-IO series device that if exploited could potentially cause critical functions like LDCM (Line Distance Communication Module) to malfunction.
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 confidenceThis is a denial-of-service vulnerability in Relion 670/650 and SAM600-IO series devices caused by improper prioritization of network traffic over protection mechanisms. The vulnerability can cause critical functions like LDCM (Line Distance Communication Module) to malfunction by allowing network traffic to interfere with protection-related communications.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify device model and firmware versionAccess the device management interface or use appropriate industrial protocol queries (IEC 61850 MMS, DNP3, or vendor-specific management protocols) to retrieve the device model number and firmware version. Compare against Relion 670, Relion 650, or SAM600-IO series.Affected if The device is a Relion 670, Relion 650, or SAM600-IO unit with firmware versions that fall within the affected range (verify with ABB vendor advisory).
-
Verify network traffic prioritization configurationExamine the device network configuration settings for QoS (Quality of Service) or traffic prioritization rules. Check if protection-related traffic (particularly LDCM communications) is configured to receive priority over general network traffic.Affected if QoS or traffic prioritization is disabled, misconfigured, or missing for protection mechanism traffic such as LDCM.
-
Inspect network segmentation statusReview network architecture and firewall/filter rules to determine whether protection-related traffic is isolated from general IT network traffic. Check if VLANs or network zones properly separate protection communications.Affected if Protection-related traffic shares the same network segment without isolation or filtering from general network traffic.
-
Check for traffic interference indicatorsMonitor network traffic patterns and device logs for evidence of LDCM communication failures, timeouts, or protection function anomalies that may correlate with high network traffic loads.Affected if LDCM or protection functions exhibit intermittent failures or timeouts, especially during periods of elevated network traffic.
A user is affected if they operate a vulnerable Relion 670/650 or SAM600-IO device without proper network traffic prioritization/segmentation protecting LDCM and protection communications.
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 dataImplement network segmentation and traffic filtering/QoS to ensure protection mechanism traffic receives priority. Contact the vendor (ABB) for firmware updates addressing this vulnerability.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2403 — 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-2403 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