Security readout for executives and security teams
Plain-English summary
CVE-2022-35255 can cause Node.js WebCrypto key generation to use weak or failed randomness. If affected software creates cryptographic keys this way, keys may be less secret than expected, undermining encryption or signing trust. The provided sources rate it critical, but do not show active exploitation.
Executive priority
Treat this as high-priority remediation for environments using Node.js WebCrypto for encryption, signing, or token trust. It is critical because weak key generation can silently compromise security assumptions, but urgency should be highest where affected runtime versions and key generation are confirmed.
Technical view
The issue is CWE-338 in Node.js WebCrypto keygen, tied to EntropySource() handling in SecretKeyGenTraits::DoKeyGen(). The code reportedly did not check failure and could use randomness not suitable for keying material. CVSS 3.1 is 9.1 with network attack vector and high confidentiality and integrity impact.
Likely exposure
Exposure is most relevant where Node.js 18, or downstream products bundling affected Node.js packages, generate WebCrypto keys. The bundle also lists multiple Node major versions, but its description specifically calls out Node.js 18, so asset validation should confirm exact affected release guidance.
Exploitation context
The bundle marks KEV as false and provides no cited evidence of active exploitation. Practical impact depends on whether applications generate security-sensitive WebCrypto keys on affected Node.js builds and whether weak key material can be abused in the application context.
Researcher notes
The main uncertainty is version scope: the description emphasizes Node.js 18, while the affected list includes many major versions with defaultStatus unaffected. Avoid broad claims without checking vendor advisories. No exploit details are needed to validate exposure; focus on runtime version, WebCrypto use, and downstream product notices.
Mitigation direction
- Inventory Node.js versions and products that bundle Node.js runtime components.
- Review Node.js, Debian, Siemens, and NetApp advisories for fixed versions or packages.
- Prioritize systems generating cryptographic keys through WebCrypto APIs.
- Rotate keys generated on confirmed affected systems where vendor guidance recommends it.
- Apply vendor updates through normal package or product update channels.
Validation and detection
- Identify services running Node.js 18 or vendor products referencing this CVE.
- Check whether the application uses WebCrypto key generation for sensitive keys.
- Confirm installed package versions against Debian or vendor advisory status.
- Review key lifecycle records for keys generated during affected runtime use.
- Document compensating controls and remaining systems awaiting vendor patches.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-338: 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 lookupCVE-2022-35255 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
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.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N3.95.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://hackerone.com/reports/1690000CVE reference
- https://cert-portal.siemens.com/productcert/pdf/ssa-332410.pdfCVE reference
- https://security.netapp.com/advisory/ntap-20230113-0002/CVE reference
- DSA-5326CVE reference · vendor-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.