CVE-2022-38138
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 · uneditedThe Triangle Microworks IEC 61850 Library (Any client or server using the C language library with a version number of 11.2.0 or earlier and any client or server using the C++, C#, or Java language library with a version number of 5.0.1 or earlier) and 60870-6 (ICCP/TASE.2) Library (Any client or server using a C++ language library with a version number of 4.4.3 or earlier) are vulnerable to access given to a small number of uninitialized pointers within their code. This could allow an attacker to target any client or server using the affected libraries to cause a denial-of-service condition.
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 confidenceThe vulnerability involves uninitialized pointers in Triangle Microworks IEC 61850 Library (C version ≤11.2.0, C++/C#/Java version ≤5.0.1) and 60870-6 ICCP/TASE.2 Library (C++ version ≤4.4.3). These uninitialized pointers can be accessed by remote attackers, potentially causing memory corruption leading to denial of service.
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 dataall versionsall versionsCVSS 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.
-
Locate Triangle Microworks IEC 61850 library filesSearch for library files named 'iec61850', 'tm61850', or similar patterns in common installation directories such as /usr/lib, /usr/local/lib, C:\Program Files, or within the application's directory structure. Also check for linked libraries in the application's binary dependencies.Affected if The library files are present in the environment
-
Identify the installed IEC 61850 library versionCheck the version metadata of the found library file - this may be in the filename, a version resource within the DLL/SO, or in accompanying documentation or manifest files. For C libraries, look for files like libiec61850.so or iec61850.dll. For C++/C#/Java, check the assembly DLL, JAR, or native binding files.Affected if The version is C library ≤11.2.0 or C++/C#/Java library ≤5.0.1
-
Locate Triangle Microworks IEC 60870-6 ICCP/TASE.2 library filesSearch for library files related to IEC 60870-6, ICCP, or TASE.2 protocols, typically named with patterns like 'icc60870', 'tase2', 'tm60870', or similar in installation directories and application dependencies.Affected if The IEC 60870-6 library files are present in the environment
-
Identify the installed IEC 60870-6 library versionCheck version metadata of the found IEC 60870-6 library file - examine version resources, filename, or accompanying documentation. For C++ versions, look for files like libtase2.so, tase2.dll, or similar naming conventions.Affected if The C++ version is ≤4.4.3
-
Confirm the application uses the library for network communicationReview application configuration, logs, or documentation to determine if the Triangle Microworks library is actively used for IEC 61850 or IEC 608-6 ICCP/TASE.2 protocol communication. Check if the application binds to ports typically used by these protocols (typically TCP ports 102, 502, or custom ports for ICCP).Affected if The library is loaded and actively processing protocol communications
The environment is affected if any Triangle Microworks IEC 61850 library (C version ≤11.2.0 or C++/C#/Java version ≤5.0.1) or IEC 60870-6 ICCP/TASE.2 library (C++ version ≤4.4.3) is present and in use.
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 · scopedUpgrade to patched versions of the affected Triangle Microworks libraries - C library version >11.2.0, C++/C#/Java library version >5.0.1, and C++ 60870-6 library version >4.4.3.
IEC 61850 Library: C language version 11.2.1+, C++/C#/Java version 5.0.2+ | IEC 60870-6 Library: C++ version 4.4.4+
- 1. Identify which Triangle Microworks libraries are in use (IEC 61850 and/or IEC 60870-6) and the specific language bindings (C, C++, C#, or Java)
- 2. Locate the library dependencies in your project configuration or build files
- 3. Obtain the fixed library versions: IEC 61850 C library version 11.2.1 or later; IEC 61850 C++/C#/Java library version 5.0.2 or later; IEC 60870-6 C++ library version 4.4.4 or later
- 4. Update the library references in your project's dependency management system (e.g., package manager, build configuration, or direct binary replacement)
- 5. Rebuild and test the application to ensure compatibility with the updated libraries
- 6. Deploy the rebuilt application to production environments
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.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 $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-38138 — 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-38138 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