-
Notifications
You must be signed in to change notification settings - Fork 357
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
Handle Component Governance issue - Upgrade System.Drawing.Common from 4.7.0 to 4.7.2 to fix the vulnerability #3111
Comments
Hi @deeguMSFT Thanks for reporting please try with version 6.0.0 seems working fine. |
Hopes it working fine no update if have please raise new request for the same.Thanks |
Hi @bhagyshricompany this fix is needed in stable for a SFI issue, so that build pipeline can pick the appropriate build number. The current version I am seeing in stable is 3.0.41, via edge.sv repo. Also, which pre-release version I should try for testing the fix, I am seeing 3.1.0-11845 in latest prerelease. I am not seeing version 6.0.0. |
Hey, why is this closed exactly? because this is an actual CVE issues. Bumping Microsoft.ApplicationInsights.AspNetCore 2.21.0 to 2.22.0 should do the job. Thank you! |
Handle Component Governance issue - Upgrade System.Drawing.Common from 4.7.0 to 4.7.2 to fix the vulnerability
There is a vulnerability (Severity: Critical) in version 4.7.0 of component System.Drawing.Common. Package dependency tree:
└─Microsoft.Azure.WebJobs.Logging.ApplicationInsights 3.0.41 - NuGet
└─Microsoft.ApplicationInsights.AspNetCore 2.21.0 - NuGet
└─Microsoft.ApplicationInsights.PerfCounterCollector 2.21.0 - NuGet
└─System.Diagnostics.PerformanceCounter 4.7.0 - NuGet
└─System.Configuration.ConfigurationManager 4.7.0 - NuGet
└─System.Security.Permissions 4.7.0 - NuGet
└─System.Windows.Extensions 4.7.0 - NuGet
└─System.Drawing.Common 4.7.0 - NuGet
The remediation steps offered by Component Governance are as follows: Upgrade System.Drawing.Common from 4.7.0 to 4.7.2 to fix the vulnerability.
The text was updated successfully, but these errors were encountered: