CVE-2022-1302
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 · uneditedIn the MZ Automation LibIEC61850 in versions prior to 1.5.1 an unauthenticated attacker can craft a goose message, which may result in a denial of service.
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 confidenceMZ Automation LibIEC61850 versions prior to 1.5.1 contain a vulnerability where an unauthenticated remote attacker can send specially crafted GOOSE (Generic Object Oriented Substation Event) messages, which are part of the IEC 61850 protocol used in SCADA/ICS environments. This malformed input triggers a denial of service condition, potentially disrupting substation automation operations.
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< 1.5.1CVSS 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 LibIEC61850 library presenceSearch for files named libiec61850, libiec61850.so, or iec61850.dll in the system, or check application dependencies/libraries for 'libiec61850' or 'MZ Automation' referencesAffected if The LibIEC61850 library is found on the system
-
Determine installed LibIEC61850 versionCheck library version through file properties, version info, or if building from source, review the version tag in the source code. Compare against the affected range: versions prior to 1.5.1 are vulnerableAffected if The installed version is earlier than 1.5.1
-
Verify GOOSE message processing is enabledReview application configuration files or source code for IEC 61850 GOOSE subscription/parsing implementation. Look for functions like 'GOOSE_parse', 'gooseSubscriber', or IEC61850_GOOSE_createAffected if The application or device processes GOOSE messages as part of IEC 61850 functionality
-
Assess network exposure of IEC 61850 servicesMonitor network traffic or review firewall rules for port 102 (IEC 61850 MMS) or observe if GOOSE messages are received on the network interfaceAffected if The system is directly accessible on the network and receives IEC 61850/GOOSE traffic from external or untrusted sources
The environment is affected if LibIEC61850 version earlier than 1.5.1 is in use and GOOSE message processing is enabled on an accessible network interface.
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.
dbcve · scoped1.5.1
Upgrade LibIEC61850 to version 1.5.1 or later. In the interim, implement network segmentation and access controls to restrict GOOSE message sources to authorized IEC 61850 devices only.
1.5.1
- Identify the current version of LibIEC61850 in use
- Obtain LibIEC61850 version 1.5.1 or later from the official distribution
- Upgrade the library to version 1.5.1
- Rebuild and redeploy any applications using the library
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.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 $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-1302 — 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-2022-1302 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