JFrog Security Research
< Back

XRAY-229142 - UA .NET Standard memory exhaustion DoS

CVE-2022-29863 | CVSS 7.5

JFrog Severity:high

Discovered ByUriya Yavnielyof the JFrog Security Research Team

Published 16 Jun, 2022 | Last updated 16 Jun, 2022

A memory exhaustion issue in UA .NET Standard and UA .NET Legacy can allow a remote attacker to perform denial of service ​

UA .NET Standard

UA .NET Legacy

UA .NET Standard (, 1.4.368.53], fixed in 1.4.368.58 UA .NET Legacy all released versions are affected. Fixed in commit 35199e43d46f0eef793cace12baa806838ddba2c ​

UA .NET Standard is an implementation of an OPC UA server in C#, provided by the OPC Foundation.

In the binary decoder when parsing an array, a 32 bit length field is being read, then an array of the matching type is being allocated. In some cases this behavior might lead to a denial of service.

A nested variant array where each element is also a nested array that has a length field set to a large number might in certain cases lead to an Exception of OutOfMemoryException. That’s because for each nested array BinaryDecoder.cs::ReadArrayElements() will try to allocate sizeof(Variant) length and then read the first variant element, but because the first variant element is also an array it will call to ReadArrayElements(). Parsing that array will behave exactly as the containing array, it will allocate an array in size of the specified length and call ReadVariant() and so on. That will lead eventually to an allocation of nesting level length * sizeof(Variant).

As the parsing process will continue, the garbage collector will be required to free up some space but it will fail, so it will be kept calling on and on while stealing running time to the other threads. Eventually the server will fail to answer requests in time.

This issue is also exists in UA .NET Legacy, the previous implementation of the OPC UA server in C#.

No PoC is supplied for this issue ​

No mitigations are supplied for this issue

UA .NET Standard advisory


< Back