Skip to main content
Mallory
LowVulnerability

CVE-2019-2814: Unauthorized Data Modification in Oracle MySQL Server InnoDB

Published Jul 23, 2019 · Updated 4 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS2.2Low · v3.1
EPSS1.3%71st percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendors
Red HatOracle Corporation
IdentifiersCVE-2019-2814CWE-269

CVE-2019-2814 is an unspecified vulnerability in the InnoDB subcomponent of Oracle MySQL Server affecting supported versions 8.0.16 and earlier. A highly privileged attacker with network access through multiple protocols can exploit the issue to perform unauthorized updates, insertions, or deletions on some data accessible to MySQL Server. Exploitation has high attack complexity and requires no user interaction. The underlying defect and vulnerable function are not publicly specified. Its CVSS 3.0 base score is 2.2, with vector CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:N.

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.

Successful exploitation compromises the integrity of some data accessible to MySQL Server by permitting unauthorized updates, insertions, or deletions. The CVSS assessment assigns low integrity impact, no confidentiality or availability impact, and unchanged scope.

Mitigation

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

No vulnerability-specific workaround is identified. Pending patching, restrict network access to MySQL to trusted systems and limit highly privileged database accounts to necessary administrators. These measures reduce exposure but do not correct the underlying vulnerability.

Remediation

Patch, then assume compromise.

Apply the MySQL security updates addressing Oracle's July 2019 Critical Patch Update. MySQL 8.0.17 includes the fix; use a currently supported release containing this correction or the appropriate vendor-patched package. For Red Hat Software Collections on RHEL 7, apply RHSA-2019:2484; for the MySQL 8.0 module on RHEL 8, apply RHSA-2019:2511. Both Red Hat updates upgrade MySQL to 8.0.17 and automatically restart the MySQL server daemon. For affected Unity Linux installations, update the mysql package under UTSA-2026-150120.

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
Oracle CorporationMysqlapplication
Red HatEnterprise Linux Eusoperating_system
Red HatEnterprise Linux Server Ausoperating_system
Red HatEnterprise Linux Server Tusoperating_system
Red HatRed Hat Enterprise Linuxoperating_system
Red HatSoftware Collectionsapplication
FAQ

Frequently asked questions

Is CVE-2019-2814 exploited in the wild?
As of Nov 14, 2026, Mallory has no reports of CVE-2019-2814 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2019-2814?
As of Nov 14, 2026, Mallory has found no public exploit for CVE-2019-2814.
Is there a patch for CVE-2019-2814?
Apply the MySQL security updates addressing Oracle's July 2019 Critical Patch Update. MySQL 8.0.17 includes the fix; use a currently supported release containing this correction or the appropriate vendor-patched package.
What products are affected by CVE-2019-2814?
Oracle Corporation Mysql, Red Hat Enterprise Linux Eus, Red Hat Enterprise Linux Server Aus, Red Hat Enterprise Linux Server Tus, Red Hat Enterprise Linux, and 1 more.
How severe is CVE-2019-2814?
CVE-2019-2814 has a CVSS v3.1 score of 2.2 (Low) and an EPSS score of 1.3% (71st percentile) as of Nov 14, 2026.
Activity feed

Recent activity

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

View more in app →
+3 more in the timeline. Sign up to see them
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.