@grpc/grpc-js: In certain configurations, getAuthContext can return unauthorized certificates as though they were authorized

[ Description ]Official description

@grpc/grpc-js implements the core functionality of gRPC purely in JavaScript, without a C++ addon. Prior to 1.13.6 and 1.14.5, getAuthContext does not distinguish authorized from unauthorized peer certificates when server credentials set requireClientCertificate to false. When applications use the returned authentication context, they can treat an unauthorized certificate as authorized, causing improper authentication. @grpc/grpc-js-xds can reach this condition when RBAC authentication is enabled in affected configurations. This issue is fixed in version 1.14.5 and 1.13.6.

[ Fixes ]Fixes and patches

• @grpc/grpc-js 1.13.6Fixed version · GitHub Advisories · npm package @grpc/grpc-js: upgrade to 1.13.6 or later (affected < 1.13.6)
• @grpc/grpc-js 1.14.5Fixed version · GitHub Advisories · npm package @grpc/grpc-js: upgrade to 1.14.5 or later (affected >= 1.14.0, < 1.14.5)

[ Packages ]Affected open-source packages

• @grpc/grpc-js npmAffected < 1.13.6 · fixed in 1.13.6 · GHSA-m9gg-hp2v-232j
• @grpc/grpc-js npmAffected >= 1.14.0, < 1.14.5 · fixed in 1.14.5 · GHSA-m9gg-hp2v-232j

[ References ]References

• github.com/grpc/grpc-node/commit/2a84ec8b01b9db68ed9d2b117a53a81449edb8ee
• github.com/grpc/grpc-node/commit/b4e0079c6d22a2adedfcac748e0bc083f783bc7c
• github.com/grpc/grpc-node/releases/tag/@grpc/grpc-js%401.14.5
• github.com/grpc/grpc-node/security/advisories/GHSA-m9gg-hp2v-232j