Skip to content
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

Potential security vulnerability with Netty dependency #2385

Closed
1 of 2 tasks
Antti-Paladin opened this issue Apr 15, 2020 · 6 comments
Closed
1 of 2 tasks

Potential security vulnerability with Netty dependency #2385

Antti-Paladin opened this issue Apr 15, 2020 · 6 comments

Comments

@Antti-Paladin
Copy link

Issue Type:

  • Bug report
  • Feature request

What happened:
There is a security vulnerability CVE-2020-11612 which concerns Netty 4.1.x before 4.1.46, and thus might affect Linkerd too (as of today the Netty version used seems to be 4.1.31 in master).

What you expected to happen:
It could be investigated if this causes a security vulnerability in Linkerd too. If so (and feasible), could update the Netty dependency to a version without the vulnerability.

Environment:

  • linkerd version: 1.7.1, but I believe this manifests with all versions using Netty 4.1.x
@olix0r
Copy link
Member

olix0r commented Apr 15, 2020

@Antti-Paladin Thanks for sharing this with us. We'll look into upgrading.

@cpretzer
Copy link
Contributor

@Antti-Paladin Thanks for this report and for helping us to keep Linkerd awesome!

I've been testing an upgrade to Netty 4.1.47 and that has a dependency on Finagle 20.4.0 and its associated libraries.

I'm held up by a finagle issue at the moment and will update this ticket when the upgrade is unblocked.

@Antti-Paladin
Copy link
Author

@cpretzer, sorry for personal ping but any news now that the finagle issue is resolved?

@cpretzer
Copy link
Contributor

Hi @Antti-Paladin , thanks for reaching out.

I'm testing the upgrade as we speak and hope to have it wrapped up today.

@Antti-Paladin
Copy link
Author

Awesome news @cpretzer, thank you! 💯

@cpretzer
Copy link
Contributor

Thanks again @Antti-Paladin this is fixed in #2386

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants