CVE-2016-7099: invalid wildcard certificate validation check

Published Sep 28, 2016
·
Updated

Fix invalid wildcard certificate validation check whereby a TLS server may be able to serve an invalid wildcard certificate for its hostname due to improper validation of . in the wildcard string.

This is a high severity defect that would allow a malicious TLS server to serve an invalid wildcard certificate for its hostname and be improperly validated by a Node.js client. This is due to a flaw in the validation of . in the wildcard name string.

Other sources

The tls.checkServerIdentity function in Node.js 0.10.x before 0.10.47, 0.12.x before 0.12.16, 4.x before 4.6.0, and 6.x before 6.7.0 does not properly handle wildcards in name fields of X.509 certificates, which allows man-in-the-middle attackers to spoof servers via a crafted certificate.

— MITRE

Affected Software

101 affected componentsFixes available
Nodejs Node.js=0.10.0
Nodejs Node.js=0.10.1
Nodejs Node.js=0.10.2
Nodejs Node.js=0.10.3
Nodejs Node.js=0.10.4
Nodejs Node.js=0.10.5
Nodejs Node.js=0.10.6
Nodejs Node.js=0.10.7
Nodejs Node.js=0.10.8
Nodejs Node.js=0.10.9
Nodejs Node.js=0.10.10
Nodejs Node.js=0.10.11
Nodejs Node.js=0.10.12
Nodejs Node.js=0.10.13
Nodejs Node.js=0.10.14
Nodejs Node.js=0.10.15
Nodejs Node.js=0.10.16
Nodejs Node.js=0.10.16-isaacs-manual
Nodejs Node.js=0.10.17
Nodejs Node.js=0.10.18
Nodejs Node.js=0.10.19
Nodejs Node.js=0.10.20
Nodejs Node.js=0.10.21
Nodejs Node.js=0.10.22
Nodejs Node.js=0.10.23
Nodejs Node.js=0.10.24
Nodejs Node.js=0.10.25
Nodejs Node.js=0.10.26
Nodejs Node.js=0.10.27
Nodejs Node.js=0.10.28
Nodejs Node.js=0.10.29
Nodejs Node.js=0.10.30
Nodejs Node.js=0.10.31
Nodejs Node.js=0.10.32
Nodejs Node.js=0.10.33
Nodejs Node.js=0.10.34
Nodejs Node.js=0.10.35
Nodejs Node.js=0.10.36
Nodejs Node.js=0.10.37
Nodejs Node.js=0.10.38
Nodejs Node.js=0.10.39
Nodejs Node.js=0.10.40
Nodejs Node.js=0.10.41
Nodejs Node.js=0.10.42
Nodejs Node.js=0.10.43
Nodejs Node.js=0.10.44
Nodejs Node.js=0.10.45
Nodejs Node.js=0.10.46
SUSE Linux Enterprise=12.0
Nodejs Node.js=6.0.0
Nodejs Node.js=6.1.0
Nodejs Node.js=6.2.0
Nodejs Node.js=6.2.1
Nodejs Node.js=6.2.2
Nodejs Node.js=6.3.0
Nodejs Node.js=6.3.1
Nodejs Node.js=6.4.0
Nodejs Node.js=6.5.0
Nodejs Node.js=6.6.0
Nodejs Node.js=0.12.0
Nodejs Node.js=0.12.1
Nodejs Node.js=0.12.2
Nodejs Node.js=0.12.3
Nodejs Node.js=0.12.4
Nodejs Node.js=0.12.5
Nodejs Node.js=0.12.6
Nodejs Node.js=0.12.7
Nodejs Node.js=0.12.8
Nodejs Node.js=0.12.9
Nodejs Node.js=0.12.10
Nodejs Node.js=0.12.11
Nodejs Node.js=0.12.12
Nodejs Node.js=0.12.13
Nodejs Node.js=0.12.14
Nodejs Node.js=0.12.15
Nodejs Node.js=4.0.0
Nodejs Node.js=4.1.0
Nodejs Node.js=4.1.1
Nodejs Node.js=4.1.2
Nodejs Node.js=4.2.0
Nodejs Node.js=4.2.1
Nodejs Node.js=4.2.2
Nodejs Node.js=4.2.3
Nodejs Node.js=4.2.4
Nodejs Node.js=4.2.5
Nodejs Node.js=4.2.6
Nodejs Node.js=4.3.0
Nodejs Node.js=4.3.1
Nodejs Node.js=4.3.2
Nodejs Node.js=4.4.0
Nodejs Node.js=4.4.1
Nodejs Node.js=4.4.2
Nodejs Node.js=4.4.3
Nodejs Node.js=4.4.4
Nodejs Node.js=4.4.5
Nodejs Node.js=4.4.6
Nodejs Node.js=4.4.7
Nodejs Node.js=4.5.0
Node.js Node.js>=4.0.0<4.6.0, >=5.0.0<6.0.0, >=6.0.0<6.7.0
4.6.06.7.0
Node.js Node.js>=4.0.0<4.6.0
4.6.0
Node.js Node.js>=6.0.0<6.7.0
6.7.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.6.0Fixed in 6.7.0
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.6.0
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.7.0
  4. Upgrade

    Upgrade Node.js to a version that resolves this vulnerability.

    Fixed in 0.10.47
  5. Upgrade

    Upgrade Node.js to a version that resolves this vulnerability.

    Fixed in 0.12.16
  6. Upgrade

    Upgrade Node.js to a version that resolves this vulnerability.

    Fixed in 4.6.0
  7. Upgrade

    Upgrade Node.js to a version that resolves this vulnerability.

    Fixed in 6.7.0

Event History

Sep 28, 2016
CVE Published
via Node.js·12:43 AM
Data Sourced
via Node.js·12:43 AM
Severity
Data Sourced
via Node.js·12:47 AM
Affected Software
Oct 10, 2016
CVE Published
via MITRE·04:00 PM
Data Sourced
via MITRE·04:00 PM
Description

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2016-7099?

CVE-2016-7099 is considered a moderate severity vulnerability, allowing potential man-in-the-middle attacks.

2

How do I fix CVE-2016-7099?

To fix CVE-2016-7099, upgrade Node.js to version 0.10.47, 0.12.16, 4.6.0 or later, or 6.7.0 or later.

3

What vulnerabilities does CVE-2016-7099 introduce?

CVE-2016-7099 introduces risks related to insufficient validation of wildcard characters in X.509 certificates.

4

Which versions of Node.js are affected by CVE-2016-7099?

CVE-2016-7099 affects Node.js versions 0.10.x before 0.10.47, 0.12.x before 0.12.16, 4.x before 4.6.0, and 6.x before 6.7.0.

5

Can CVE-2016-7099 be exploited remotely?

Yes, CVE-2016-7099 can be exploited remotely by attackers using crafted certificates to spoof server identities.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203