LiveActive security incident?Get immediate response
CVE Record

CVE-2022-32223: Node.js is vulnerable to Hijack Execution Flow: DLL Hijacking under certain conditions on Windows platforms...

Node.js is vulnerable to Hijack Execution Flow: DLL Hijacking under certain conditions on Windows platforms.This vulnerability can be exploited if the victim has the following dependencies on a Windows machine:* OpenSSL has been installed and “C:\Program Files\Common Files\SSL\openssl.cnf” exists.Whenever the above conditions are present, `node.exe` will search for `providers.dll` in the current user directory.After that, `node.exe` will try to search for `providers.dll` by the DLL Search Order in Windows.It is possible for an attacker to place the malicious file `providers.dll` under a variety of paths and exploit this vulnerability.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This issue affects Node.js on Windows when a specific OpenSSL configuration file exists. In that setup, node.exe may load a providers.dll from unsafe search locations, allowing code execution if an attacker can place a malicious DLL where Node will search.

Executive priority

Prioritize Windows servers and developer workstations where Node.js runs with meaningful privileges. This is not described as remotely exploitable by itself, but it can turn weak local file placement controls into execution under Node.js process privileges.

Technical view

CVE-2022-32223 is a CWE-427 DLL search order issue in Node.js for Windows. The described trigger requires OpenSSL installed with C:\Program Files\Common Files\SSL\openssl.cnf present. Under those conditions, node.exe searches for providers.dll in the current user directory and then Windows DLL search paths.

Likely exposure

Exposure is most likely on Windows systems running affected Node.js versions 4.0 through 18.0 where the named OpenSSL configuration file exists. Non-Windows systems are not described as affected in the provided sources.

Exploitation context

The sources describe a conditional DLL hijacking path but do not cite active exploitation. CISA KEV status is false in the supplied bundle. Practical exploitation depends on attacker ability to place a DLL in a searched location.

Researcher notes

The core uncertainty is product-specific exposure: the CVE depends on Windows, affected Node.js versions, and a specific OpenSSL configuration path. The provided bundle does not include CVSS, detailed fixed-version mapping, or evidence of exploitation in the wild.

Mitigation direction

  • Apply the relevant Node.js July 2022 security release or later vendor-supported version.
  • Check Node.js vendor guidance before choosing a fixed version for legacy runtimes.
  • Remove unnecessary OpenSSL installations or configuration files where operationally safe.
  • Restrict write access to directories used by affected Node.js processes.
  • Review NetApp guidance if Node.js is bundled in NetApp-managed products.

Validation and detection

  • Inventory Windows hosts running Node.js versions 4.0 through 18.0.
  • Check whether C:\Program Files\Common Files\SSL\openssl.cnf exists on those hosts.
  • Confirm production Node.js binaries are updated beyond affected vendor releases.
  • Review writable working directories used by Node.js services and scheduled tasks.
  • Check endpoint telemetry for unexpected providers.dll loads by node.exe.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-427: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-32223 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
NodeJSNode4.0, 5.0, 6.0, 7.0, 8.0, 9.0, 10.0, 11.0, 12.0, 13.0, 14.0, 15.0, 16.0, 17.0, 18.0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-427 · source CWE mapping

Uncontrolled Search Path Element

Uncontrolled Search Path Element represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.