BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2021
CVE-2021-22939High confidence

NodeJS Node — Improper Certificate Validation

NodeJS · Node

5.3MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:High, raised one band.upgradedsince 30 Apr 2025

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 14.73% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs NodeJS Node and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Alpine, Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

10 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Alpine v3.23v3.23 · communitynodejs-currentVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.16.6.2-r0Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.23v3.23 · mainnodejsVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.14.17.5-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.22v3.22 · communitynodejs-currentVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.16.6.2-r0Alpine Security Database ↗Source updated 11 Sep 2026
Alpine v3.22v3.22 · mainnodejsVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.14.17.5-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.21v3.21 · communitynodejs-currentVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.16.6.2-r0Alpine Security Database ↗Source updated 19 Aug 2026
Alpine v3.21v3.21 · mainnodejsVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.14.17.5-r0Alpine Security Database ↗Source updated 3 Oct 2026
Debian trixietrixie · sourcenodejsVendor fix publishedDebian records a fixed source-package version for this release.12.22.5~dfsg-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcenodejsVendor fix publishedDebian records a fixed source-package version for this release.12.22.5~dfsg-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcenodejsVendor fix publishedDebian records a fixed source-package version for this release.12.22.5~dfsg-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcenodejsVendor fix publishedDebian records a fixed source-package version for this release.12.22.5~dfsg-1Debian Security Tracker ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
SSA-389290 · CSAF 2.0 · revision 1 · finalSiemens ProductCERTSSA-389290: Third-Party Component Vulnerabilities in SINEC INS
1 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SINEC INS
Summary
If the Node.js https API was used incorrectly and "undefined" was in passed for the "rejectUnauthorized" parameter, no error was returned and connections to servers with an expired certificate would have been accepted.
Remediation
Update to V1.0.1.1 or later version
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2021-10068

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

If the Node.js https API was used incorrectly and "undefined" was in passed for the "rejectUnauthorized" parameter, no error was returned and connections to servers with an expired certificate would have been accepted.

What

If the Node.js https API was used incorrectly and "undefined" was in passed for the "rejectUnauthorized" parameter, no error was returned and connections to servers with an expired certificate would have been accepted.

Why

The product does not validate, or incorrectly validates, a certificate.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

If the Node.js https API was used incorrectly and "undefined" was in passed for the "rejectUnauthorized" parameter, no error was returned and connections to servers with an expired certificate would have been accepted.

Why

The product does not validate, or incorrectly validates, a certificate.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
a network path → Improper Certificate Validation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-295 ↗

CWE-295: Improper Certificate Validation. The product does not validate, or incorrectly validates, a certificate.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.ILowIntegrity impact: A successful attack can cause a limited loss.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-295Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2023-0856IBM QRadar SIEM: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2022-1083Node.js: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Node.js ausnutzen, um beliebigen Programmcode auszuführen, einen Cross-Site-Scripting Angriff durchzuführen, einen Denial of Service Zustand herzustellen und Sicherheitsmaßnahmen zu umgehen.

Official advisory ↗
BSI · German · WID-SEC-2022-0029Elasticsearch und Kibana: Mehrere Schwachstellen

Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Elasticsearch und Kibana ausnutzen, um beliebigen Programmcode auszuführen, um Informationen offenzulegen, um einen Cross-Site Scripting Angriff durchzuführen und um Administratorrechte zu erlangen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20210818Security Bulletin 18 Aug 2021

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 18 Aug 2021, published on 18 August 2021. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-1051Multiples vulnérabilités dans les produits IBM

7178033 du 05 décembre 2024 https://www.ibm.com/support/pages/node/7178033 Bulletin de sécurité IBM 7178054 du 06 décembre 2024 https://www.ibm.com/support/pages/node/7178054 Référence CVE CVE-2020-28500 https://www.cve.org/CVERecord?id=CVE-2020-28500 Référence CVE CVE-2020-8203 https://www.cve.org/CVERecord?id=CVE-2020-8203 Référence CVE CVE-2021-22918 https://www.cve.org/CVERecord?id=CVE-2021-22918 Référence CVE CVE-2021-22921 https://www.cve.org/CVERecord?id=CVE-2021-22921 Référence CVE CVE-2021-22930 https://www.cve.org/CVERecord?id=CVE-2021-22930 Référence CVE CVE-2021-22931 https://www.cve.org/CVERecord?id=CVE-2021-22931 Référence CVE CVE-2021-22939 https://www.cve.org/CVERecord?id=CVE-2021-22939 Référence CVE CVE-2021-22940 https://www.cve.org/CVERecord?id=CVE-2021-22940 Référence CVE CVE-2021-22959 https://www.cve.org/CVERecord?id=CVE-2021-22959 Référence CVE CVE-2021-22960 https://www.cve.org/CVERecord?id=CVE-2021-22960 Référence CVE CVE-2021-23337 https://www.cve.org/CVERecord?id=CVE-2021-23337 Référence CVE CVE-2021-29425 https://www.cve.org/CVERecord?id=CVE-2021-29425 Référence CVE CVE-2021-29892 https://www.cve.org/CVERecord?id=CVE-2021-29892 Référence CVE CVE-2021-36690 https://www.cve.org/CVERecord?id=CVE-2021-36690 Référence CVE CVE-2021-44531 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2022-AVI-510Multiples vulnérabilités dans IBM QRadar

ecord?id=CVE-2020-13632 Référence CVE CVE-2020-15168 https://www.cve.org/CVERecord?id=CVE-2020-15168 Référence CVE CVE-2020-15358 https://www.cve.org/CVERecord?id=CVE-2020-15358 Référence CVE CVE-2020-28469 https://www.cve.org/CVERecord?id=CVE-2020-28469 Référence CVE CVE-2020-7788 https://www.cve.org/CVERecord?id=CVE-2020-7788 Référence CVE CVE-2020-9327 https://www.cve.org/CVERecord?id=CVE-2020-9327 Référence CVE CVE-2021-22918 https://www.cve.org/CVERecord?id=CVE-2021-22918 Référence CVE CVE-2021-22930 https://www.cve.org/CVERecord?id=CVE-2021-22930 Référence CVE CVE-2021-22931 https://www.cve.org/CVERecord?id=CVE-2021-22931 Référence CVE CVE-2021-22939 https://www.cve.org/CVERecord?id=CVE-2021-22939 Référence CVE CVE-2021-22940 https://www.cve.org/CVERecord?id=CVE-2021-22940 Référence CVE CVE-2021-23343 https://www.cve.org/CVERecord?id=CVE-2021-23343 Référence CVE CVE-2021-23362 https://www.cve.org/CVERecord?id=CVE-2021-23362 Référence CVE CVE-2021-27290 https://www.cve.org/CVERecord?id=CVE-2021-27290 Référence CVE CVE-2021-32803 https://www.cve.org/CVERecord?id=CVE-2021-32803 Référence CVE CVE-2021-32804 https://www.cve.org/CVERecord?id=CVE-2021-32804 Référence CVE CVE-2021-33502 https://www.cve.org/CVERecord?id=CVE-2021-33502 Référence CVE CVE-2021-3672 https://www.cve.org/CVERecord?id=C

Official advisory ↗
CERT-FR · French · CERTFR-2022-AVI-216Multiples vulnérabilités dans les produits Siemens

d?id=CVE-2021-22918 Référence CVE CVE-2021-22921 https://www.cve.org/CVERecord?id=CVE-2021-22921 Référence CVE CVE-2021-22922 https://www.cve.org/CVERecord?id=CVE-2021-22922 Référence CVE CVE-2021-22923 https://www.cve.org/CVERecord?id=CVE-2021-22923 Référence CVE CVE-2021-22924 https://www.cve.org/CVERecord?id=CVE-2021-22924 Référence CVE CVE-2021-22925 https://www.cve.org/CVERecord?id=CVE-2021-22925 Référence CVE CVE-2021-22926 https://www.cve.org/CVERecord?id=CVE-2021-22926 Référence CVE CVE-2021-22930 https://www.cve.org/CVERecord?id=CVE-2021-22930 Référence CVE CVE-2021-22931 https://www.cve.org/CVERecord?id=CVE-2021-22931 Référence CVE CVE-2021-22939 https://www.cve.org/CVERecord?id=CVE-2021-22939 Référence CVE CVE-2021-22940 https://www.cve.org/CVERecord?id=CVE-2021-22940 Référence CVE CVE-2021-22945 https://www.cve.org/CVERecord?id=CVE-2021-22945 Référence CVE CVE-2021-22946 https://www.cve.org/CVERecord?id=CVE-2021-22946 Référence CVE CVE-2021-22947 https://www.cve.org/CVERecord?id=CVE-2021-22947 Référence CVE CVE-2021-23362 https://www.cve.org/CVERecord?id=CVE-2021-23362 Référence CVE CVE-2021-23840 https://www.cve.org/CVERecord?id=CVE-2021-23840 Référence CVE CVE-2021-25173 https://www.cve.org/CVERecord?id=CVE-2021-25173 Référence CVE CVE-2021-25174 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2021-AVI-943Multiples vulnérabilités dans les produits IBM

d?id=CVE-2021-21345 Référence CVE CVE-2021-21346 https://www.cve.org/CVERecord?id=CVE-2021-21346 Référence CVE CVE-2021-21347 https://www.cve.org/CVERecord?id=CVE-2021-21347 Référence CVE CVE-2021-21348 https://www.cve.org/CVERecord?id=CVE-2021-21348 Référence CVE CVE-2021-21349 https://www.cve.org/CVERecord?id=CVE-2021-21349 Référence CVE CVE-2021-21350 https://www.cve.org/CVERecord?id=CVE-2021-21350 Référence CVE CVE-2021-21351 https://www.cve.org/CVERecord?id=CVE-2021-21351 Référence CVE CVE-2021-22930 https://www.cve.org/CVERecord?id=CVE-2021-22930 Référence CVE CVE-2021-22931 https://www.cve.org/CVERecord?id=CVE-2021-22931 Référence CVE CVE-2021-22939 https://www.cve.org/CVERecord?id=CVE-2021-22939 Référence CVE CVE-2021-22940 https://www.cve.org/CVERecord?id=CVE-2021-22940 Référence CVE CVE-2021-23368 https://www.cve.org/CVERecord?id=CVE-2021-23368 Référence CVE CVE-2021-29060 https://www.cve.org/CVERecord?id=CVE-2021-29060 Référence CVE CVE-2021-29505 https://www.cve.org/CVERecord?id=CVE-2021-29505 Référence CVE CVE-2021-29923 https://www.cve.org/CVERecord?id=CVE-2021-29923 Référence CVE CVE-2021-32027 https://www.cve.org/CVERecord?id=CVE-2021-32027 Référence CVE CVE-2021-32028 https://www.cve.org/CVERecord?id=CVE-2021-32028 Référence CVE CVE-2021-32029 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2021-AVI-932Multiples vulnérabilités dans les produits IBM

De multiples vulnérabilités ont été découvertes dans les produits IBM. Certaines d'entre elles permettent à un attaquant de provoquer un déni de service à distance, un contournement de la politique de sécurité et une atteinte à l'intégrité des données.

Official advisory ↗
CERT-FR · French · CERTFR-2021-AVI-670Multiples vulnérabilités dans les produits Elastic

De multiples vulnérabilités ont été découvertes dans les produits Elastic. Elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, une élévation de privilèges et une injection de code indirecte à distance (XSS).

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-010675Node.js https API における証明書検証に関する脆弱性

Node.js https API には、証明書検証に関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
SINEC INS
Fixed
Update to V1.0.1.1 or later version
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 16 Aug 2021 · Last source change 30 Apr 2025, 22:24 UTC · CWE-295 · Improper Certificate Validation

CVE recordCVE.org · 5.1
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2021-10068
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
CWE sourceCNA
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    4.0 < 4.*; 5.0 < 5.*; 6.0 < 6.*; 7.0 < 7.*; 8.0 < 8.*; 9.0 < 9.*; 10.0 < 10.*; 11.0 < 11.* · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    After
    4.0 < 4.*; 5.0 < 5.*; 6.0 < 6.*; 7.0 < 7.*; 8.0 < 8.*; 9.0 < 9.*; 10.0 < 10.*; 11.0 < 11.* · Fixed: Update to V1.0.1.1 or later version
    Siemens ProductCERT ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2021-10068↗Patch or update reference↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Public exploit reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2021-22939 · cve.blacktree.nl