Skip to content

Bump MongoDB.Driver from 2.13.1 to 2.15.0 and Microsoft.AspNetCore.Http from 2.1.0 to 2.2.0#608

Merged
michaelcfanning merged 8 commits into
mainfrom
bump-mongodb-package
Apr 14, 2022
Merged

Bump MongoDB.Driver from 2.13.1 to 2.15.0 and Microsoft.AspNetCore.Http from 2.1.0 to 2.2.0#608
michaelcfanning merged 8 commits into
mainfrom
bump-mongodb-package

Conversation

@eddynaka

@eddynaka eddynaka commented Apr 11, 2022

Copy link
Copy Markdown
Collaborator

Changes

This change will fix the following issues:

As you can see, you cannot see Microsoft.AspNetCore.Http version 2.1.0 in the changes because it is a reference from the package Microsoft.NET.Sdk.Functions -> Microsoft.Azure.WebJobs.Extensions.Http -> Microsoft.AspNetCore.Http

For significant contributions please make sure you have completed the following items:

  • ReleaseHistory.md updated for non-trivial changes
  • Added unit tests

Comment thread azure-pipelines.yml
# inputs:
# targetPath: bld/bin/AnyCPU_Debug/Tests.Security/netcoreapp3.1/
# artifactName: Tests.Security
- task: ComponentGovernanceComponentDetection@0 No newline at end of file

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

ComponentGovernanceComponentDetection@0

this will guarantee that ComponentGovernance can always track this repository

<PackageReference Include="GoogleApi" Version="4.0.4" />
<PackageReference Include="Microsoft.Security.Utilities" Version="1.1.0" />
<PackageReference Include="MongoDB.Driver" Version="2.13.1" />
<PackageReference Include="MongoDB.Driver" Version="2.15.0" />

@eddynaka eddynaka Apr 11, 2022

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

2.15.0

Version 2.15.0 contains the updated version of SharpCompress (0.30.1), which does not have a vulnerability.

<None Remove="Properties\PublishProfiles\**" />
</ItemGroup>
<ItemGroup>
<PackageReference Include="Microsoft.AspNetCore.Http" Version="2.2.2" />

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

2.2.2

2.2.2 contains a fix for the vulnerability found in 2.1.0:
https://access.redhat.com/security/cve/CVE-2020-1045

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

there are no release notes for the PR, which is customer impacting, potentially, because runtime components are changing.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Just updated and added some detail in the description

@michaelcfanning michaelcfanning left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

🕐

@eddynaka eddynaka changed the title Fixing component governance issues Bump MongoDB.Driver from 2.13.2 to 2.14.0 and Microsoft.AspNetCore.Http package from 2.1.0 to 2.2.0 Apr 11, 2022
@eddynaka eddynaka changed the title Bump MongoDB.Driver from 2.13.2 to 2.14.0 and Microsoft.AspNetCore.Http package from 2.1.0 to 2.2.0 Bump MongoDB.Driver from 2.13.2 to 2.14.0 and Microsoft.AspNetCore.Http from 2.1.0 to 2.2.0 Apr 11, 2022
Comment thread Src/ReleaseHistory.md Outdated

## Unreleased

- Bump MongoDB.Driver from 2.13.2 to 2.14.0 and Microsoft.AspNetCore.Http from 2.1.0 to 2.2.0. [#608](https://github.com/microsoft/sarif-pattern-matcher/pull/608)

@michaelcfanning michaelcfanning Apr 11, 2022

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

2.13.2

this version is wrong, s/be 2.13.1 #Closed

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Fixed

Comment thread Src/ReleaseHistory.md Outdated

## Unreleased

- Bump MongoDB.Driver from 2.13.2 to 2.14.0 and Microsoft.AspNetCore.Http from 2.1.0 to 2.2.0. [#608](https://github.com/microsoft/sarif-pattern-matcher/pull/608)

@michaelcfanning michaelcfanning Apr 11, 2022

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

14

version is wrong #Closed

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

fixed.
I mistakenly used the version of ElfSharp (it was in my head).

@eddynaka eddynaka changed the title Bump MongoDB.Driver from 2.13.2 to 2.14.0 and Microsoft.AspNetCore.Http from 2.1.0 to 2.2.0 Bump MongoDB.Driver from 2.13.1 to 2.14.0 and Microsoft.AspNetCore.Http from 2.1.0 to 2.2.0 Apr 11, 2022
@eddynaka eddynaka changed the title Bump MongoDB.Driver from 2.13.1 to 2.14.0 and Microsoft.AspNetCore.Http from 2.1.0 to 2.2.0 Bump MongoDB.Driver from 2.13.1 to 2.15.0 and Microsoft.AspNetCore.Http from 2.1.0 to 2.2.0 Apr 11, 2022
Comment thread Src/ReleaseHistory.md

## Unreleased

- Bump MongoDB.Driver from 2.13.1 to 2.15.0 and Microsoft.AspNetCore.Http from 2.1.0 to 2.2.0. [#608](https://github.com/microsoft/sarif-pattern-matcher/pull/608)

@cfaucon cfaucon Apr 12, 2022

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Do we have existing tests in both the security project and spam function that exercise a code path that will leverage these dependencies? i.e. will we know if somehow we break ourselves due to any binding or other runtime behaviors. #Closed

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

for the mongodb package, we have an end-to-end test
for the http package, its the azure function. I was able to run and debug.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

actually, our mongodb validator is disabled due to not being signed. so, we won't face any impact.

Comment thread Src/ReleaseHistory.md

## Unreleased

- Bump MongoDB.Driver from 2.13.1 to 2.15.0 and Microsoft.AspNetCore.Http from 2.1.0 to 2.2.0. [#608](https://github.com/microsoft/sarif-pattern-matcher/pull/608)

@cfaucon cfaucon Apr 12, 2022

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Should the CVEs be linked here? I notice most all release line items are very factual and explain just the change and not rationale as to the why. If that is intended I suppose CVEs don't need to be historically captured here.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

One of my first iterations I had added, then I removed to simplify and added this to the PR.

The rationale: you as a customer who is using will only see the release notes if you face a problem. For things like vulnerabilities, I think you wouldn't come, so, it's why I omitted in the end.

@cfaucon cfaucon left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

:shipit:

@michaelcfanning michaelcfanning left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

:shipit:

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

Successfully merging this pull request may close these issues.

3 participants