@grpc/grpc-js is vulnerable to Improper Certificate Validation
74
CVE Score
High
Improper Certificate Validation
BaseServerInterceptingCall.getAuthContext() in @grpc/grpc-js returns the peer's TLS certificate data for any TLS connection without checking the socket's authorized flag. Servers that create credentials with requireClientCertificate set to false and then rely on getAuthContext for authentication, such as @grpc/grpc-js-xds RBAC policies, cannot tell an unauthorized or self-signed client certificate from an authorized one. This lets an unauthorized client be treated as though it presented a trusted certificate. The fix checks socket.authorized before returning peer certificate data from getAuthContext.
Upgrade the @grpc/grpc-js library to the patch version.
You are affected if you are using a version that falls within the vulnerable range and you configure server credentials with requireClientCertificate set to false while relying on getAuthContext for authentication or RBAC decisions.
1.14.0 - 1.14.4
Fixed in 1.14.5@grpc/grpc-js is vulnerable to Improper Certificate Validation in versions 1.14.0 - 1.14.4.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.