-
Notifications
You must be signed in to change notification settings - Fork 286
Netty dependency version is vulnerable #423
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I found a few problems with this issue:
|
Ping, is this a concern to any maintainer? |
It's not a high priority for a couple of reasons:
We will eventually bump the Netty version in our pom file. |
Fixed in #438 |
@hiranya911 the problematic pulled netty dependency is not a direct dependency of firebase-admin. firebase-admin 6.13 is pulling netty via two different paths:
and
The direct dependency of firebase-admin is netty 4.1.49, which is not affected by CVE-2020-11612. The problematic netty is the second one since I just want to confirm that your assessment that it's not an issue because you only use the client part of the library to connect to RTDB is still valid for this second path. What about
|
#438 has upgraded our dependency on Firestore to the latest available version. If Firestore is still using an older version of Netty it needs to be fixed at https://github.com/googleapis/java-firestore. Either way, you can always specify a more recent version of Netty in your own application dependency list, and override the older versions getting pulled via transitive dependencies. |
About your second point, i don't think you can. that was the first thing i tried: overriding the buggy version of
Overriding higher in the dependency chain also didn't work due to similar errors and it also has its own set of risks About your first point, i will check if the updates fix the problem and if not i will report the bug upstream, I was just trying to get an idea if the next update on firebase-admin would be a "do it when you can" or if it should be "do it immediatly since 6.13 has a bad security flaw" |
Why not override the version of netty instead of grpc-netty-shaded? You can also add a dependency exclusion for netty through firebase-admin. |
do you mean the direct dependency of firebase-admin? the one you updated in #438 ? if so, because the direct dependency of netty does not have any critical CVEs opened to it. Like I mentioned in my first post, firebase-admin has 2 different dependencies on netty. The direct one (the one you updated) is fine, no CVEs. the problem is the shaded/indirect one: If by "netty instead of grpc-netty-shaded" you mean something else please explain further. But in short, the bad CVEs are in About excluding grpc-netty-shaded, I have no idea where these classes are used so I can't really tell if this will create NoClassDefFoundErrors at runtime |
You need to override the dependencies as higher in the tree as possible. With firebase-admin:6.13.0 and google-cloud-firestore:1.34.0, my dependency tree comes out like this:
|
ok. if you say it's ok to update |
Feel free to always use the latest minor and patch versions of Firestore and Storage. |
implementation ("com.google.firebase:firebase-admin:9.1.1") Provides transitive vulnerable dependency maven:io.netty:netty-codec:4.1.84.Final |
Hey folks,
You are using a vulnerable version of Netty with an impressive 9.8/10 criticality score. Suggest patching ASAP to
4.1.50.Final
which should have binary compatibility as they are on modified semverI'd submit a PR but I'm awaiting a confirmation on signing the Google CLA and I assume you want to move fast here. Tests seemed to pass in my local fork though
Cheers!
The text was updated successfully, but these errors were encountered: