dbcve.org
Libiec61850Application · Mz Automation

CVE-2022-2971

HIGH · 7.5 CVSS v3.1 Published 2022-09-23
Fix available
A fix is available. Upgrade to 1.5.0 or later.
See remediation →
84/100
Remediation priority · High
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
MZ Automation's libIEC61850 (versions 1.4 and prior; version 1.5 prior to commit a3b04b7bc4872a5a39e5de3fdc5fbde52c09e10e) accesses a resource using an incompatible type, which could allow an attacker to crash the server with a malicious payload.

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

libIEC61850 contains a type confusion vulnerability where the software accesses a resource using an incompatible type (CWE-199). This occurs in the IEC 61850 protocol implementation when the code expects one data type but receives another, allowing a remote attacker to crash the server with a malicious payload. The vulnerability affects versions 1.4 and prior, and version 1.5 before commit a3b04b7bc4872a5a39e5de3fdc5fbde52c09e10e.

MitigationUpgrade libIEC61850 to version 1.5 at or after commit a3b04b7bc4872a5a39e5de3fdc5fbde52c09e10e which contains the fix for the type mismatch. Alternatively, apply the specific patch from that commit to correct the incompatible type access.

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
Libiec61850Application
Affected:< 1.5.0

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate libIEC61850 library
    Search for libiec61850 shared libraries or source code in your application dependencies, build artifacts, or installed packages. Check your dependency manifest (package.json, requirements.txt, pom.xml, Cargo.toml, etc.) for 'libiec61850' or 'iec61850'.
    Affected if libIEC61850 is present in your environment and is version 1.5.0 or older, or the exact version cannot be determined from your dependencies.
  2. Determine installed version
    Examine the version string of the libiec61850 library or check your software bill of materials (SBOM) for the exact version number. Compare against the affected range: versions 1.4.x and earlier, or version 1.5.x prior to the fix commit.
    Affected if The library version is 1.4.x or earlier, or is 1.5.x without the fix commit a3b04b7bc4872a5a39e5de3fdc5fbde52c09e10e applied.
  3. Verify IEC 61850 server is active
    Check if your application or device exposes an IEC 61850 server service (MMS, GOOSE, or SCL file processing). Look for configuration files (ICD, IED, SCD files) or process listening on IEC 61850 ports (typically 102/tcp or 2222/tcp for MMS).
    Affected if An IEC 61850 server is running and processing client data, as the vulnerability is triggered during protocol data handling.
  4. Inspect data type handling code
    If you have access to source code, search for DataAttribute, DataSet, or type-related structures in iec61850 source files. Look for places where received protocol data types are cast without proper validation checks.
    Affected if The code processes incoming IEC 61850 data without validating type compatibility before access, making it vulnerable to type confusion.

Your environment is affected if libIEC61850 version is below 1.5.0 or unpatched, AND you are running an IEC 61850 server that processes client data.

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 1.5.0 or later
Fixed in 1.5.0
Interim mitigation

Upgrade libIEC61850 to version 1.5 at or after commit a3b04b7bc4872a5a39e5de3fdc5fbde52c09e10e which contains the fix for the type mismatch. Alternatively, apply the specific patch from that commit to correct the incompatible type access.

Recommended fix High confidence

libIEC61850 version 1.5.0 or later

  1. 1. Identify the current version of libIEC61850 in use by checking the codebase or build configuration
  2. 2. Download or clone libIEC61850 version 1.5.0 or later from the official repository (https://github.com/mz-automation/libIEC61850)
  3. 3. Replace the vulnerable library files with the updated version 1.5.0+
  4. 4. Rebuild and redeploy the IEC 61850 server application with the updated library
  5. 5. Verify the server starts successfully and test IEC 61850 functionality

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

Fix this in Libiec61850 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,900
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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