dbcve.org
Microscada X Sys600Application · Hitachienergy

CVE-2025-39203

MEDIUM · 6.5 CVSS v3.1 Published 2025-06-24
Fix available
A fix is available. Upgrade to 10.7 or later.
See remediation →
71/100
Remediation priority · Elevated
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 vulnerability exists in the IEC 61850 of the MicroSCADA X SYS600 product. An IEC 61850-8 crafted message content from IED or remote system can cause a denial of service resulting in disconnection loop.

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

A vulnerability in the IEC 61850 implementation of ABB MicroSCADA X SYS600 allows remote attackers to send crafted IEC 61850-8 messages from an IED or remote system that cause a denial of service, creating a persistent disconnection loop that disrupts SCADA operations.

MitigationImplement strict input validation and message content filtering on IEC 61850-8 traffic, add rate limiting and connection state monitoring, and consider network segmentation to restrict IEC 61850 traffic to trusted sources.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Microscada X Sys600Application
Affected:>= 10.5, < 10.7

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

CVSS:3.1/AV:N/AC:L/PR:L/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 the installed MicroSCADA X SYS600 version
    Check the product version through the system information panel in the MicroSCADA X SYS600 management interface, or review the installed software package details via the Windows Programs and Features control panel or system registry
    Affected if The installed version is 10.5.0 through 10.6.x (any version >= 10.5 and < 10.7)
  2. Verify IEC 61850-8 protocol is enabled
    Inspect the MicroSCADA X SYS600 protocol configuration settings to confirm IEC 61850-8 (MMS) communication is enabled as an active protocol driver in the system configuration
    Affected if IEC 61850-8 protocol is configured and active in the SCADA system
  3. Check network exposure of IEC 61850 services
    Review network configuration and firewall rules to determine if the IEC 61850-8 service ports (typically TCP port 102 for MMS) are exposed to untrusted network segments or external systems
    Affected if IEC 61850-8 services are accessible from network segments that contain untrusted or attacker-controlled IEDs or remote systems
  4. Look for disconnection loop symptoms
    Monitor system logs, event logs, and SCADA operator displays for repeated IEC 61850 connection failures, persistent reconnection attempts, or cyclic disconnection patterns involving IEDs communicating via IEC 61850-8
    Affected if Multiple IEC 61850 devices are experiencing repeated disconnection and reconnection cycles that persist despite manual intervention

A system is affected if it runs MicroSCADA X SYS600 version 10.5 through 10.6.x with IEC 61850-8 protocol enabled and accessible to remote systems, particularly if disconnection loops are observed.

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.

dbcve · scoped
Upgrade available Upgrade to 10.7 or later
Fixed in 10.7
Interim mitigation

Implement strict input validation and message content filtering on IEC 61850-8 traffic, add rate limiting and connection state monitoring, and consider network segmentation to restrict IEC 61850 traffic to trusted sources.

Recommended fix High confidence

MicroSCADA X SYS600 version 10.7

  1. Back up the current MicroSCADA X SYS600 configuration, databases, and all relevant data
  2. Review the version 10.7 release notes and upgrade documentation for any specific migration requirements or prerequisites
  3. Download the MicroSCADA X SYS600 version 10.7 installer from the Hitachi Energy support portal
  4. Test the upgrade in a non-production/staging environment first to verify compatibility with your specific configuration
  5. Schedule a maintenance window for the production upgrade
  6. Stop all MicroSCADA X SYS600 services according to the documented shutdown procedure
  7. Install version 10.7 following the official upgrade instructions
  8. Start the upgraded services and verify the system initializes correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Microscada X Sys600 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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