Is CVE-2024-57086 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2024-57086 being exploited in the wild.

How severe is CVE-2024-57086?

Low severity, with a CVSS score of 3.1, published 6 February 2025.

Which products and versions are affected?

node-opcua-alarm-condition (npm) SEMVER:introduced=0,fixed=2.137.0.

Is there a fix for CVE-2024-57086?

Yes. node-opcua-alarm-condition (npm): upgrade to 2.137.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2024-57086 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2024-57086?

Check whether you run node-opcua-alarm-condition (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2024-57086: node-opcua-alarm-condition prototype pollution in fieldsToJson

CVE-2024-57086 · Severity: low · CVSS 3.1 · Published 2025-02-06

node-opcua-alarm-condition is a Node.js library that implements OPC UA alarm and condition functionality for industrial IoT systems. A prototype pollution vulnerability in the fieldsToJson function allows an attacker to send a crafted payload over the network, causing the application to crash or become unresponsive, disrupting industrial operations and system availability.

Vendors: npm.

Quick answers

Is CVE-2024-57086 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2024-57086 being exploited in the wild.
How severe is CVE-2024-57086?: Low severity, with a CVSS score of 3.1, published 6 February 2025.
Which products and versions are affected?: node-opcua-alarm-condition (npm) SEMVER:introduced=0,fixed=2.137.0.
Is there a fix for CVE-2024-57086?: Yes. node-opcua-alarm-condition (npm): upgrade to 2.137.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2024-57086 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2024-57086?: Check whether you run node-opcua-alarm-condition (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

node-opcua-alarm-condition (npm): upgrade to 2.137.0 or later
```
npm install node-opcua-alarm-condition@2.137.0
```

Technical details

The vulnerability is a prototype pollution flaw (CWE-1321) in the fieldsToJson function of node-opcua-alarm-condition that allows attackers to inject malicious properties into JavaScript objects. The vulnerability is triggered by supplying a crafted payload and requires only network connectivity with no authentication or user interaction needed. An attacker can exploit this to cause a Denial of Service (DoS) by crashing or degrading the application performance. The vulnerability affects all versions up to and including 2.134.0; it has been patched in version 2.137.0 and later.

Affected products

node-opcua node-opcua-alarm-condition 0 through 2.136.x

Identifiers

CVE-2024-57086
GHSA-gvwq-6fmx-28xm

Timeline

2025-02-05: disclosed: CVE-2024-57086 published
2025-02-06: advisory: GHSA-gvwq-6fmx-28xm advisory published
2025-02-06: patched: Fixed in version 2.137.0
2025-04-10: other: GitHub advisory reviewed and confirmed fix verified by community

References

https://github.com/node-opcua/node-opcua/issues/1433

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.