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

Update logback-classic and netty dependency #2367

Closed
woglinde opened this issue Jun 30, 2022 · 3 comments · Fixed by #2419
Closed

Update logback-classic and netty dependency #2367

woglinde opened this issue Jun 30, 2022 · 3 comments · Fixed by #2419

Comments

@woglinde
Copy link

Right now the logback-classic version is at 1.2.8 and netty is at 4.1.76. Against both CVE's with a moderate score exists, which lets secrutiy scanner like trivy or blackduck to complain about them.
Would be nice if both dependency could be updated to the latest version and a hotfix release could be made.

@ghost ghost added the Needs: Triage 🔍 label Jun 30, 2022
@trask
Copy link
Member

trask commented Jun 30, 2022

hi @woglinde!

logback-classic is being updated in #2365

it looks like Application Insights isn't affected by the netty CVE since that only affects Java 6 and older (assuming we're looking at the same one): Azure/azure-sdk-for-java#29295

we are getting netty as a transitive dependency from Azure SDK, so we'll probably plan on waiting until they update that dependency

@woglinde
Copy link
Author

woglinde commented Jul 1, 2022

Hi @trask,

thanks for looking into and yes I know both CVEs have a moderate score are not that easily useable, but some companies have a strict policy about it and always writing exception files is not fun either.

@trask
Copy link
Member

trask commented Jul 1, 2022

it looks like Azure SDKs updated it a few days ago Azure/azure-sdk-for-java#29638, we'll pull in the latest Azure SDK dependencies as soon as it is released

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

Successfully merging a pull request may close this issue.

2 participants