From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@buildroot.org
Cc: Daniel Price <daniel.price@gmail.com>, Martin Bark <martin@barkynet.com>
Subject: Re: [Buildroot] [PATCH] package/nodejs: security bump to version 14.18.3
Date: Fri, 28 Jan 2022 18:03:26 +0100 [thread overview]
Message-ID: <87wnij7py9.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20220114103825.1529-1-peter@korsgaard.com> (Peter Korsgaard's message of "Fri, 14 Jan 2022 11:38:24 +0100")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
> Fixes the following security issues:
> Improper handling of URI Subject Alternative Names (Medium)(CVE-2021-44531)
> Accepting arbitrary Subject Alternative Name (SAN) types, unless a PKI is
> specifically defined to use a particular SAN type, can result in bypassing
> name-constrained intermediates. Node.js was accepting URI SAN types, which
> PKIs are often not defined to use. Additionally, when a protocol allows URI
> SANs, Node.js did not match the URI correctly.
> Certificate Verification Bypass via String Injection (Medium)(CVE-2021-44532)
> Node.js converts SANs (Subject Alternative Names) to a string format. It
> uses this string to check peer certificates against hostnames when
> validating connections. The string format was subject to an injection
> vulnerability when name constraints were used within a certificate chain,
> allowing the bypass of these name constraints.
> Incorrect handling of certificate subject and issuer fields (Medium)(CVE-2021-44533)
> Node.js did not handle multi-value Relative Distinguished Names correctly.
> Attackers could craft certificate subjects containing a single-value
> Relative Distinguished Name that would be interpreted as a multi-value
> Relative Distinguished Name, for example, in order to inject a Common Name
> that would allow bypassing the certificate subject verification.
> Prototype pollution via console.table properties (Low)(CVE-2022-21824)
> Due to the formatting logic of the console.table() function it was not safe
> to allow user controlled input to be passed to the properties parameter
> while simultaneously passing a plain object with at least one property as
> the first parameter, which could be __proto__. The prototype pollution has
> very limited control, in that it only allows an empty string to be assigned
> numerical keys of the object prototype.
> For details, see the advisory:
> https://nodejs.org/en/blog/vulnerability/jan-2022-security-releases/
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Committed to 2021.11.x, thanks.
For 2021.02.x I will instead bump to 12.22.9 which contains the same
fixes.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-01-28 17:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 10:38 [Buildroot] [PATCH] package/nodejs: security bump to version 14.18.3 Peter Korsgaard
2022-01-17 21:37 ` Yann E. MORIN
2022-01-28 17:03 ` Peter Korsgaard [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wnij7py9.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=daniel.price@gmail.com \
--cc=martin@barkynet.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox