Skip to main content
Mallory
MediumVulnerability

CVE-2019-2920: Partial DOS in Oracle MySQL Connector/ODBC (CVE-2019-2920)

Published Oct 16, 2019 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.3Medium · v3.1
EPSS2.3%83rd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendors
Oracle CorporationCanonical
IdentifiersCVE-2019-2920CWE-400

CVE-2019-2920 is a vulnerability in Oracle MySQL Connectors, specifically in the Connector/ODBC component, affecting versions 5.3.13 and prior, and 8.0.17 and prior. The vulnerability is easily exploitable by an unauthenticated attacker with network access via multiple protocols. Successful exploitation can result in a partial denial of service (DOS) of the MySQL Connectors, impacting availability. The vulnerability does not require user interaction or privileges, and is rated with a CVSS 3.0 base score of 5.3, indicating moderate severity with primary impact on availability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An unauthenticated remote attacker can cause a partial denial of service in affected MySQL Connectors, potentially disrupting database connectivity for applications relying on Connector/ODBC. There is no impact to confidentiality or integrity, but availability of the connector may be degraded, leading to service interruptions.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, restrict network access to the MySQL Connectors to trusted hosts only, and monitor for abnormal service interruptions. Consider implementing network-level controls (e.g., firewalls, segmentation) to limit exposure until patches can be applied.

Remediation

Patch, then assume compromise.

Apply the patches provided by Oracle in the October 2019 Critical Patch Update. Upgrade MySQL Connector/ODBC to a version later than 5.3.13 or 8.0.17, as appropriate for your deployment. Ensure all Oracle MySQL components are updated to the latest supported versions to mitigate this and other vulnerabilities.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
CanonicalUbuntu Linuxoperating_system
Oracle CorporationMysqlapplication
FAQ

Frequently asked questions

Is CVE-2019-2920 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2019-2920 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2019-2920?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2019-2920.
Is there a patch for CVE-2019-2920?
Apply the patches provided by Oracle in the October 2019 Critical Patch Update. Upgrade MySQL Connector/ODBC to a version later than 5.3.13 or 8.0.17, as appropriate for your deployment.
What products are affected by CVE-2019-2920?
Oracle Corporation Mysql and Canonical Ubuntu Linux.
How severe is CVE-2019-2920?
CVE-2019-2920 has a CVSS v3.1 score of 5.3 (Medium) and an EPSS score of 2.3% (83rd percentile) as of Oct 16, 2026.
Activity feed

Recent activity

1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.