Odbc Driver for SQL Server vulnerabilitiesRanked by how likely they are to be used.
Odbc Driver for SQL Server is made by Microsoft. We track 23 published vulnerabilities in it, across 12 versions. None of them is on the list of flaws known to be exploited today. If you run Odbc Driver for SQL Server, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Odbc Driver for SQL Server vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Odbc Driver for SQL Server's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Odbc Driver for SQL Server flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 2.4%CVE-2024-28931High
Microsoft ODBC Driver for SQL Server Remote Code Execution Vulnerability
- 2.4%CVE-2024-28934High
Microsoft ODBC Driver for SQL Server Remote Code Execution Vulnerability
- 2.4%CVE-2024-28933High
Microsoft ODBC Driver for SQL Server Remote Code Execution Vulnerability
- 2.4%CVE-2024-28936High
Microsoft ODBC Driver for SQL Server Remote Code Execution Vulnerability
- 2.4%CVE-2024-28932High
Microsoft ODBC Driver for SQL Server Remote Code Execution Vulnerability
- 2.4%CVE-2024-28929High
Microsoft ODBC Driver for SQL Server Remote Code Execution Vulnerability
- 2.4%CVE-2024-28930High
Microsoft ODBC Driver for SQL Server Remote Code Execution Vulnerability
- 2.4%CVE-2024-28935High
Microsoft ODBC Driver for SQL Server Remote Code Execution Vulnerability
- 2.4%CVE-2024-28943High
Microsoft ODBC Driver for SQL Server Remote Code Execution Vulnerability
- 2.4%CVE-2024-29043High
Microsoft ODBC Driver for SQL Server Remote Code Execution Vulnerability
Running Odbc Driver for SQL Server? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Microsoft ODBC Driver for SQL Server Remote Code Execution Vulnerability
- Matched to
- Odbc Driver for SQL Server on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 23 published vulnerabilities listed under the name Odbc Driver for SQL Server, across 12 versions.
None of Odbc Driver for SQL Server's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Odbc Driver for SQL Server. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.