CVE-2022-32222

OpenSSL configuration hijacking via embedded build path

Published Jul 14, 2022 · Updated Apr 30, 2025

Configuration hijacking in Node.js allows local users to alter another user's OpenSSL settings during process startup. Node.js embeds a build-time OPENSSLDIR path and loads openssl.cnf from /home/iojs/build/ws/out/Release/obj.target/deps/openssl instead of the system directory. The issue affects Linux 18.0.0 through 18.4.0 and macOS 18.0.0 through 18.9.0 on shared hosts where an attacker controls the iojs home path.

CVSS severity5.3
Medium
EPSS probability2.15%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Configuration hijacking in Node.js allows local users to alter another user's OpenSSL settings during process startup. Node.js embeds a build-time OPENSSLDIR path and loads openssl.cnf from /home/iojs/build/ws/out/Release/obj.target/deps/openssl instead of the system directory. The issue affects Linux 18.0.0 through 18.4.0 and macOS 18.0.0 through 18.9.0 on shared hosts where an attacker controls the iojs home path.

The record

CVE
CVE-2022-32222
Published
Jul 14, 2022
Updated
Apr 30, 2025
Vendor
Node.js
Product
Node.js
Classifications
CWE-310, CWE-427
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Jul 14, 2022CVE publishedPublication date reported by the CVE source.
  2. Apr 30, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=10.0 <10.*
  2. Affected versionversion=11.0 <11.*
  3. Affected versionversion=12.0 <12.*
  4. Affected versionversion=13.0 <13.*
  5. Affected versionversion=14.0 <14.20.0
  6. Affected versionversion=15.0 <15.*
  7. Affected versionversion=16.0 <16.20.0
  8. Affected versionversion=17.0 <17.*
  9. Affected versionversion=18.0 <18.9.1
  10. Affected versionversion=4.0 <4.*
  11. Affected versionversion=5.0 <5.*
  12. Affected versionversion=6.0 <6.*
  13. Affected versionversion=7.0 <7.*
  14. Affected versionversion=8.0 <8.*
  15. Affected versionversion=9.0 <9.*

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

Node.js · Node.jsversion=10.0 <10.*; version=11.0 <11.*; version=12.0 <12.*; version=13.0 <13.*; version=14.0 <14.20.0; version=15.0 <15.*; version=16.0 <16.20.0; version=17.0 <17.*; version=18.0 <18.9.1; version=4.0 <4.*; version=5.0 <5.*; version=6.0 <6.*; version=7.0 <7.*; version=8.0 <8.*; version=9.0 <9.*

Published CVSS scores

5.3NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-310Cryptographic Issues
CWE-427Uncontrolled Search Path Element

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo