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

[Bug] CI Pipeline Does Not Fail when Vulnerable Dependencies Found #493 #497

Merged
merged 8 commits into from
Jul 17, 2022

Conversation

VladislavAntonyuk
Copy link
Collaborator

@VladislavAntonyuk VladislavAntonyuk commented Jul 15, 2022

Description of Change

Fail pipeline if has any vulnerability

Linked Issues

PR Checklist

Additional information

@VladislavAntonyuk
Copy link
Collaborator Author

As we have 3 vulnerabilities, how can we move forward with this PR? Some of them were fixed by .NET MAUI team

@jfversluis
Copy link
Member

Oh good one! Why don't we get dependabot alerts on this repo? That should also catch these, right?

@VladislavAntonyuk
Copy link
Collaborator Author

VladislavAntonyuk commented Jul 15, 2022

Added dependabot. I added the flag CheckDependencies and enabled it. we can set it to false to skip checks on each build and set it to true to enable it during the release build.

@VladislavAntonyuk
Copy link
Collaborator Author

Question №2, should we check Transitive vulnerabilities? we cannot fix them.
Question №3. Should we check it in solution or only src projects? We have vulnerabilities in CommunityToolkit.Maui.UnitTests

@VladislavAntonyuk VladislavAntonyuk force-pushed the 493-fail-on-vulnerable-dependencies branch 3 times, most recently from bc540a1 to c3154ec Compare July 15, 2022 13:39
@VladislavAntonyuk VladislavAntonyuk force-pushed the 493-fail-on-vulnerable-dependencies branch 4 times, most recently from c3a8c15 to 2bd8aaf Compare July 15, 2022 14:59
@VladislavAntonyuk VladislavAntonyuk force-pushed the 493-fail-on-vulnerable-dependencies branch from 2bd8aaf to 7ec73eb Compare July 15, 2022 15:22
@TheCodeTraveler
Copy link
Collaborator

TheCodeTraveler commented Jul 15, 2022

Thanks Vlad!

As we have 3 vulnerabilities, how can we move forward with this PR? Some of them were fixed by .NET MAUI team

The 3 vulnerabilities are in the *.UnitTest projects. I agree with your approach of adding/updating the NuGet Packages in the UnitTest csprojs.

Question №2, should we check Transitive vulnerabilities? we cannot fix them.

We should! We can always add an updated version of the specific NuGet Package that has fixed the vulnerability, like you've done by adding a direct reference to Newtonsoft.Json

Question №3. Should we check it in solution or only src projects? We have vulnerabilities in CommunityToolkit.Maui.UnitTests

I vote to check the entire solution. It's good to ensure we avoid vulnerabilities in every csproj, even if it's a Sample App or a Unit Test.

@jfversluis
Copy link
Member

I agree with everything Brandon said!

@VladislavAntonyuk
Copy link
Collaborator Author

Copy link
Collaborator

@TheCodeTraveler TheCodeTraveler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking good! Thanks Vlad!

I had just a small bit of feedback around the new environment variable in the pipeline.

azure-pipelines.yml Outdated Show resolved Hide resolved
@TheCodeTraveler TheCodeTraveler enabled auto-merge (squash) July 17, 2022 17:05
Copy link
Collaborator

@TheCodeTraveler TheCodeTraveler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Vlad!!

@TheCodeTraveler TheCodeTraveler merged commit 5ade8c2 into main Jul 17, 2022
@TheCodeTraveler TheCodeTraveler deleted the 493-fail-on-vulnerable-dependencies branch July 17, 2022 17:05
@github-actions github-actions bot locked and limited conversation to collaborators Nov 22, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug] CI Pipeline Does Not Fail when Vulnerable Dependencies Found
3 participants