[GHSA-m494-w24q-6f7w] JDBC Driver for SQL Server has improper input validation issue#6449
Merged
advisory-database[bot] merged 1 commit intourielcos/advisory-improvement-6449from Nov 24, 2025
Conversation
github-actions
bot
changed the base branch from
main
to
urielcos/advisory-improvement-6449
advisory-database
bot
merged commit 8814b04
into
urielcos/advisory-improvement-6449
4 checks passed
Contributor
|
Hi @urielcos! Thank you so much for contributing to the GitHub Advisory Database. This database is free, open, and accessible to all, and it's people like you who make it great. Thanks for choosing to help others. We hope you send in more contributions in the future! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates
Comments
The fix is related to how authentication is made using certificates.
Such method of auth wasn't added until version 8.3.0 as seen here: microsoft/mssql-jdbc@9732e1b#diff-45367b99a1951943bfecfc7765e80df687967aa56286a5b2e039f77cd9a0e118 and in this PR: microsoft/mssql-jdbc#1284
versions below aren't susceptible to this CVE