CVE-2025-0814
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 · uneditedCWE-20: Improper Input Validation vulnerability exists that could cause Denial-of-Service of the network services running on the product when malicious IEC61850-MMS packets are sent to the device. The core functionality of the breaker remains intact during the attack.
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 confidenceImproper input validation vulnerability (CWE-20) in IEC61850-MMS packet processing allows remote attackers to cause denial-of-service of network services by sending malformed IEC61850-MMS packets. The core breaker functionality remains operational during the attack.
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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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 IEC61850-MMS service exposureReview network configuration and firewall rules to determine if any system is exposing IEC61850-MMS protocol services (typically on TCP ports 102, 2222, or MMS-specific ports) to network accessAffected if IEC61850-MMS services are exposed to untrusted networks without proper filtering
-
Confirm IEC61850-MMS protocol processing is enabledExamine the device or software configuration to verify if IEC61850-MMS protocol handling is active. Check product documentation or runtime status for MMS stack/module presenceAffected if IEC61850-MMS protocol processing feature is enabled and running
-
Check for signs of DoS from malformed packetsReview system and network logs for patterns of service disruptions, crashes, or unusual error messages related to IEC61850-MMS packet handling. Look for time-correlated issues with MMS trafficAffected if Service disruptions occur coincidentally with IEC61850-MMS traffic and logs show malformed packet errors
-
Identify affected product and versionLocate the installed product name and version that processes IEC61850-MMS packets. Consult vendor documentation or system inventory for exact version informationAffected if The product version is within a vulnerable range that has not yet received patches for this CVE
An environment is affected if it runs software with IEC61850-MMS protocol processing enabled and exposed to network traffic, and the installed version matches the vulnerable range for CVE-2025-0814
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 proper input validation on IEC61850-MMS packets at the protocol parsing layer, and consider network-level protections such as firewall rules or IDS signatures to filter malformed MMS traffic.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0814 — 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-0814 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