dbcve.org
Libiec61850Application · Mz Automation

CVE-2022-2972

CRITICAL · 9.8 CVSS v3.1 Published 2022-09-23
Fix available
A fix is available. Upgrade to 1.5.0 or later.
See remediation →
100/100
Remediation priority · Urgent
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) is vulnerable to a stack-based buffer overflow, which could allow an attacker to crash the device or remotely execute arbitrary code.

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 · high confidence

libIEC61850 versions 1.4 and prior, and version 1.5 before commit a3b04b7bc4872a5a39e5de3fdc5fbde52c09e10e, contains a stack-based buffer overflow vulnerability that could allow an attacker to crash the device or achieve remote code execution.

MitigationUpgrade libIEC61850 to version 1.5 at or after commit a3b04b7bc4872a5a39e5de3fdc5fbde52c09e10e, or apply that specific commit patch, to remediate the stack-based buffer overflow vulnerability.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 if libIEC61850 is deployed
    Search for libiec61850 libraries, header files, or binaries in your system. Common locations include /usr/lib/, /usr/local/lib/, or project dependencies. Check your application's dependency list or build configuration files.
    Affected if libIEC61850 is found and its version is below 1.5.0
  2. Determine the installed version of libIEC61850
    Check the library version by running 'strings' on the binary, inspecting version headers, checking package metadata, or reviewing the source code if locally compiled. Look for version strings like '1.4', '1.5', or specific git commit hashes.
    Affected if The version is 1.4 or prior, or version 1.5 without commit a3b04b7bc4872a5a39e5de3fdc5fbde52c09e10e
  3. Identify if your application uses the affected IEC 61850 server components
    Review your application code to determine if it initializes an IEC 61850 server (MMS, GOOSE, or SV server). The vulnerability is in server-side processing, so check for IedServer_create or similar API calls.
    Affected if Your application uses libIEC61850 as an IEC 61850 server and the library version is vulnerable
  4. Check for the specific patched commit in version 1.5
    If running version 1.5.x, inspect the git commit history or check the source files for the presence of commit a3b04b7bc4872a5a39e5de3fdc5fbde52c09e10e. This can be verified by checking the source repository or build metadata.
    Affected if Running version 1.5 but the patched commit is not present

You are affected if libIEC61850 is deployed and your installed version is below 1.5.0 (or is version 1.5 without the specific commit fix).

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, or apply that specific commit patch, to remediate the stack-based buffer overflow vulnerability.

Recommended fix High confidence

libIEC61850 1.5.0 or later

  1. 1. Identify the current version of libIEC61850 in use by checking project dependencies or library files
  2. 2. Download libIEC61850 version 1.5.0 or later from the official GitHub repository (https://github.com/mz-automation/libIEC61850)
  3. 3. Review the release notes for version 1.5.0 to confirm the security fix for CVE-2022-2972 is included
  4. 4. Replace the existing libIEC61850 library files with the new version
  5. 5. Recompile any applications that link against libIEC61850
  6. 6. Test the application to ensure functionality is maintained after the upgrade
  7. 7. Deploy the updated version to production environments

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

Fix this in Libiec61850 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
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,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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