CVE-2016-7099
published 2016-10-10CVE-2016-7099: 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…
PriorityP430medium5.9CVSS 3.0
AVNACHPRNUINSUCNIHAN
EPSS
2.84%
85.2th percentile
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.
Affected
106 ranges· showing 25
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | nodejs | < nodejs 4.6.0~dfsg-1 (bookworm) | nodejs 4.6.0~dfsg-1 (bookworm) |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
| nodejs | node.js | — | — |
CVSS provenance
nvdv3.05.9MEDIUMCVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
nvdv2.04.3MEDIUMAV:N/AC:M/Au:N/C:N/I:P/A:N
osv5.9MEDIUM
vendor_debian5.9LOW
vendor_redhat5.9MEDIUM
vendor_ubuntu5.9MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-79cw-cghj-vx7w: The tls
ghsa_unreviewed·2022-05-14
CVE-2016-7099 [MEDIUM] GHSA-79cw-cghj-vx7w: The tls
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.
OSV
nodejs vulnerabilities
osv·2021-03-15·CVSS 5.9
CVE-2016-7099 [MEDIUM] nodejs vulnerabilities
nodejs vulnerabilities
Alexander Minozhenko and James Bunton discovered that Node.js did not
properly handle wildcards in name fields of X.509 TLS certificates. An
attacker could use this vulnerability to execute a machine-in-the-middle-
attack. This issue only affected Ubuntu 14.04 ESM and 16.04 ESM. (CVE-2016-7099)
It was discovered that Node.js incorrectly handled certain NAPTR responses.
A remote attacker could possibly use this issue to cause applications using
Node.js to crash, resulting in a denial of service. This issue only affected
Ubuntu 16.04 ESM. (CVE-2017-1000381)
Nikita Skovoroda discovered that Node.js mishandled certain input, leading
to an out of bounds write. An attacker could use this vulnerability to
cause a denial of service (crash) or possibly execute arbitrary co
OSV
CVE-2016-7099: The tls
osv·2016-10-10·CVSS 5.9
CVE-2016-7099 [MEDIUM] CVE-2016-7099: The tls
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.
Ubuntu
Node.js vulnerabilities
vendor_ubuntu·2021-03-15·CVSS 5.9
CVE-2018-7160 [MEDIUM] Node.js vulnerabilities
Title: Node.js vulnerabilities
Summary: Several security issues were fixed in Node.js.
Alexander Minozhenko and James Bunton discovered that Node.js did not
properly handle wildcards in name fields of X.509 TLS certificates. An
attacker could use this vulnerability to execute a machine-in-the-middle-
attack. This issue only affected Ubuntu 14.04 ESM and 16.04 ESM. (CVE-2016-7099)
It was discovered that Node.js incorrectly handled certain NAPTR responses.
A remote attacker could possibly use this issue to cause applications using
Node.js to crash, resulting in a denial of service. This issue only affected
Ubuntu 16.04 ESM. (CVE-2017-1000381)
Nikita Skovoroda discovered that Node.js mishandled certain input, leading
to an out of bounds write. An attacker could use this vulnerability to
c
Red Hat
nodejs: wildcard certificates not properly validated
vendor_redhat·2016-09-28·CVSS 5.9
CVE-2016-7099 [MEDIUM] nodejs: wildcard certificates not properly validated
nodejs: wildcard certificates not properly validated
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.
It was found that Node.js' tls.checkServerIdentity() function did not properly validate server certificates containing wildcards. A malicious TLS server could use this flaw to get a specially crafted certificate accepted by a Node.js TLS client.
Package: nodejs (Red Hat Mobile Application Platform 4) - Not affected
Package: nodejs010-nodejs (Red Hat OpenShift Enterprise 2) - Will not fix
Package: nodejs (Red Hat OpenShift Enterprise 3) - Not affec
Debian
CVE-2016-7099: nodejs - The tls.checkServerIdentity function in Node.js 0.10.x before 0.10.47, 0.12.x be...
vendor_debian·2016·CVSS 5.9
CVE-2016-7099 [MEDIUM] CVE-2016-7099: nodejs - The tls.checkServerIdentity function in Node.js 0.10.x before 0.10.47, 0.12.x be...
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.
Scope: local
bookworm: resolved (fixed in 4.6.0~dfsg-1)
bullseye: resolved (fixed in 4.6.0~dfsg-1)
forky: resolved (fixed in 4.6.0~dfsg-1)
sid: resolved (fixed in 4.6.0~dfsg-1)
trixie: resolved (fixed in 4.6.0~dfsg-1)
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2016-7099 nodejs: wildcard certificates not properly validated
bugzilla·2016-09-28·CVSS 5.9
CVE-2016-7099 [MEDIUM] CVE-2016-7099 nodejs: wildcard certificates not properly validated
CVE-2016-7099 nodejs: wildcard certificates not properly validated
The following flaw was reported in Node.js:
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.
External References:
https://nodejs.org/en/blog/vulnerability/september-2016-security-releases/
Discussion:
Created nodejs tracking bugs for this issue:
Affects: fedora-all [bug 1379922]
---
Upstream commit:
0.10.x
https://github.com/nodejs/node/commit/0d7e21ee7bcc79046f898f8c202d2ec87d23d711
4.x
https://github.com/nodejs/node/commit/3ff82deb2c3bd580d64be75dbafe460393c952fb
---
Marking nodejs010-nodejs as WONTFIX becaus
Bugzilla
CVE-2016-7099 nodejs: wildcard certificates not properly validated [fedora-all]
bugzilla·2016-09-28·CVSS 5.9
CVE-2016-7099 [MEDIUM] CVE-2016-7099 nodejs: wildcard certificates not properly validated [fedora-all]
CVE-2016-7099 nodejs: wildcard certificates not properly validated [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions o
http://lists.opensuse.org/opensuse-security-announce/2016-10/msg00013.htmlhttp://rhn.redhat.com/errata/RHSA-2017-0002.htmlhttp://www.securityfocus.com/bid/93191https://github.com/nodejs/node/commit/743f0c916469f3129dfae406fa104dc46782e20bhttps://nodejs.org/en/blog/vulnerability/september-2016-security-releases/http://lists.opensuse.org/opensuse-security-announce/2016-10/msg00013.htmlhttp://rhn.redhat.com/errata/RHSA-2017-0002.htmlhttp://www.securityfocus.com/bid/93191https://github.com/nodejs/node/commit/743f0c916469f3129dfae406fa104dc46782e20bhttps://nodejs.org/en/blog/vulnerability/september-2016-security-releases/
2016-10-10
Published