Skip to content

Update dependency Microsoft.Data.SqlClient to 5.1.3 [SECURITY]#112

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/nuget-microsoft.data.sqlclient-vulnerability
Open

Update dependency Microsoft.Data.SqlClient to 5.1.3 [SECURITY]#112
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/nuget-microsoft.data.sqlclient-vulnerability

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Aug 6, 2024

This PR contains the following updates:

Package Change Age Confidence
Microsoft.Data.SqlClient (source) 5.1.15.1.3 age confidence

GitHub Vulnerability Alerts

CVE-2024-0056

Microsoft.Data.SqlClient and System.Data.SqlClient SQL Data Provider Security Feature Bypass Vulnerability


Release Notes

dotnet/sqlclient (Microsoft.Data.SqlClient)

v5.1.3

This update brings the below changes over the previous release:

Fixed
  • Fixed encryption downgrade issue. CVE-2024-0056
  • Fixed certificate chain validation logic flow.

v5.1.2

This update brings the following changes since the 5.1.6 release:

Fixed
  • Fixed possible NullPointerException during socket receive (PR #​3285)
  • Fixed inconsistencies between source and reference projects (PR #​3180)
Changed

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot changed the title Update dependency Microsoft.Data.SqlClient to v5.1.3 [SECURITY] Update dependency Microsoft.Data.SqlClient to 5.1.3 [SECURITY] Aug 28, 2024
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.

0 participants