First published: Tue Oct 11 2022(Updated: )
The 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.
Credit: ics-cert@hq.dhs.gov
Affected Software | Affected Version | How to fix |
---|---|---|
Triangle Microworks TMW Library: IEC 60870-6 (ICCP/Tase.2) | ||
Trianglemicroworks IEC 61850 software Library | ||
Triangle Microworks TMW Library: IEC 61850 Any client or server using the C language library with a version number of 11.2.0 or earlier. Any client or server using the C++, C#, or Java language library with a version number of 5.0.1 or earlier | ||
Triangle Microworks Any client or server using the C language library | ||
Triangle Microworks Any client or server using the C++, C#, or Java language library | ||
Triangle Microworks TMW Library: IEC 60870-6 (ICCP/Tase.2) | ||
Triangle Microworks Any client or server using the C++, C#, or Java language library |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-38138 has a high severity rating, which indicates significant risk to affected systems.
To remediate CVE-2022-38138, upgrade to the latest version of the Triangle Microworks libraries that are not affected by this vulnerability.
CVE-2022-38138 affects the Triangle Microworks IEC 61850 Library version 11.2.0 and earlier, and IEC 60870-6 Library version 4.4.3 and earlier.
CVE-2022-38138 can be exploited by attackers to compromise data integrity or lead to unauthorized access to systems using the affected libraries.
Currently, there are no official workarounds for CVE-2022-38138; the best approach is to upgrade to a secure version of the libraries.