LiveActive security incident?Get immediate response
CVE Record

CVE-2021-2014: Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: PAM Auth Plugin).

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: PAM Auth Plugin). Supported versions that are affected are 5.7.32 and prior. Easily exploitable vulnerability allows high privileged 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.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).

MediumCVSS 4.9Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-2014 is a denial-of-service issue in Oracle MySQL Server's PAM authentication plugin. An attacker already holding high privileges and network access could cause MySQL Server to hang or crash repeatedly. The business impact is service availability, not data theft or tampering based on the provided sources.

Executive priority

Prioritize remediation for production databases where outage would affect revenue, customer access, or core operations. This is not evidenced as data compromise, but database downtime can still be business-critical.

Technical view

Oracle describes this as an easily exploitable MySQL Server vulnerability affecting 5.7.32 and prior in Server: PAM Auth Plugin. CVSS 3.1 is 4.9: network attack vector, low complexity, high privileges required, no user interaction, unchanged scope, and high availability impact only.

Likely exposure

Exposure is most relevant for MySQL Server 5.7.32 and prior where the PAM authentication plugin is present, especially if MySQL is reachable over a network by privileged users or service accounts.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. Practical abuse requires network access and high privileges, reducing likelihood, but a successful attack can fully disrupt database availability.

Researcher notes

The provided sources give product, component, version range, and CVSS details but not root-cause specifics or exploit mechanics. Avoid assuming broader MySQL branches, exact fixed versions, or active exploitation without consulting vendor advisories.

Mitigation direction

  • Apply Oracle January 2021 CPU guidance or downstream vendor fixed packages.
  • Upgrade affected MySQL Server 5.7.32 and prior installations per vendor guidance.
  • Restrict MySQL network access to trusted administrative and application sources.
  • Review and reduce high-privileged MySQL accounts where operationally possible.
  • Monitor for repeated MySQL crashes, hangs, or unexplained availability loss.

Validation and detection

  • Inventory MySQL Server versions and identify any 5.7.32 or earlier deployments.
  • Confirm whether the PAM authentication plugin is enabled or packaged.
  • Check exposure paths for network access to MySQL Server.
  • Review privileged database accounts and service account access.
  • Correlate MySQL error logs with crash or hang events.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2021-2014 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.9 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H1.23.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.9Medium
CVSS 3.1 vector shape for CVE-2021-2014Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Oracle CorporationMySQL Server5.7.32 and priorListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.