Quick answers
- Is CVE-2022-24375 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2022-24375 being exploited in the wild.
- How severe is CVE-2022-24375?
- Low severity, with a CVSS score of 3.1, published 25 August 2022.
- Which products and versions are affected?
- node-opcua (npm) SEMVER:introduced=0,fixed=2.74.0.
- Is there a fix for CVE-2022-24375?
- Yes. node-opcua (npm): upgrade to 2.74.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2022-24375 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2022-24375?
- Check whether you run node-opcua (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 (npm): upgrade to 2.74.0 or later
npm install node-opcua@2.74.0
Technical details
The vulnerability is a denial of service (DoS) attack via uncontrolled resource consumption (CWE-400). An attacker can bypass memory consumption limitations by repeatedly sending CloseSession requests with the deleteSubscription parameter set to False, causing the node-opcua server to exhaust available memory. The attack requires network access to the OPC UA server but no authentication or user interaction. A successful exploit results in service unavailability. The vulnerability was patched in version 2.74.0, released in August 2022.
Affected products
- node-opcua node-opcua before 2.74.0
Identifiers
- CVE-2022-24375
- GHSA-vh4f-fgpp-x8x2
Timeline
- 2022-08-25: disclosed
- 2022-08-13: patched: Fix merged in PR #1182