dbcve.org
MySQLDatabase / datastore · Oracle

CVE-2020-2804

MEDIUM · 5.9 CVSS v3.1 Published 2020-04-15
Fix available
A fix is available. Upgrade to after 8.0.19 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Memcached). Supported versions that are affected are 5.6.47 and prior, 5.7.29 and prior and 8.0.19 and prior. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.0 Base Score 5.9 (Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Vulnerability in MySQL Server's Memcached component allows unauthenticated remote attackers with network access to cause a denial of service by crashing or hanging the MySQL Server. The attack is characterized as difficult to exploit but requires no authentication.

MitigationUpgrade MySQL Server to a patched version (5.6.48+, 5.7.30+, or 8.0.20+) to address this vulnerability. If Memcached component is not required, consider disabling it.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MySQLDatabase / datastore
Affected:>= 5.6.0, <= 5.6.47>= 5.7.0, <= 5.7.29>= 8.0.0, <= 8.0.19
FedoraOperating system
Affected:= 30= 31= 32
Ubuntu LinuxOperating system
Affected:= 16.04= 18.04= 19.10= 20.04
Active Iq Unified ManagerApplication
Affected:>= 7.3>= 9.5
Oncommand InsightApplication
Affected:all versions
Oncommand Workflow AutomationApplication
Affected:all versions
SnapcenterApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed MySQL Server version
    Run `mysql --version` or `mysqld --version` from command line, or query `SELECT VERSION();` inside the MySQL client
    Affected if Version is 5.6.0 through 5.6.47, 5.7.0 through 5.7.29, or 8.0.0 through 8.0.19
  2. Verify if Memcached component is loaded in MySQL
    Query `SELECT * FROM mysql.component;` or run `SHOW PLUGINS;` looking for memcached-related entries
    Affected if The memcached plugin or daemon_memcached component is present and enabled
  3. Check MySQL configuration for Memcached settings
    Inspect MySQL config files (my.cnf or my.ini) in /etc/, /etc/mysql/, or the data directory for lines containing 'daemon_memcached' or 'memcached' under [mysqld] section
    Affected if Configuration contains daemon_memcached option with port or other memcached settings defined
  4. Check for running memcached-related processes
    Run `ps aux | grep -i memcached` or check if port 11211 (default memcached port) is listening with `netstat -tlnp | grep 11211`
    Affected if A memcached process is running or port 11211 is open and associated with MySQL

User is affected if their MySQL version falls within the affected ranges AND the Memcached component/plugin is enabled in their MySQL installation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 8.0.19
Interim mitigation

Upgrade MySQL Server to a patched version (5.6.48+, 5.7.30+, or 8.0.20+) to address this vulnerability. If Memcached component is not required, consider disabling it.

Fix this in MySQL Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-2804 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-2804 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data