Cyber Resilience

CVE-2025-30687

Oracle Mysql Server 8.0.0 – 8.0.41

Published
15 April 2025
Modified
03 November 2025
Patch / advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0075 51th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2025-30687 is a medium-severity Incorrect Permission Assignment for Critical Resource (CWE-732) vulnerability in Oracle Mysql Server. Its CVSS base score is 6.5 (Medium).

Operationally, ranked in the top 49% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-5 (Denial-of-service Protection) and SI-2 (Flaw Remediation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.0-8.0.41, 8.4.0-8.4.4 and 9.0.0-9.2.0. Easily exploitable vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful…

more

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 6.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).

CWE(s)

Related Threats

CVEs Like This One

CVE-2025-21523Same product: Oracle Mysql Server
CVE-2025-30682Same product: Oracle Mysql Server
CVE-2025-21566Same product: Oracle Mysql Server
CVE-2025-21584Same product: Oracle Mysql Server
CVE-2025-21579Same product: Oracle Mysql Server
CVE-2025-30685Same product: Oracle Mysql Server
CVE-2025-21581Same product: Oracle Mysql Server
CVE-2025-30688Same product: Oracle Mysql Server
CVE-2025-30683Same product: Oracle Mysql Server
CVE-2025-30684Same product: Oracle Mysql Server

Affected Assets

oracle
mysql server
8.0.0 — 8.0.41 · 8.4.0 — 8.4.4 · 9.0.0 — 9.2.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SC-5 Denial-of-service Protection
  • AC-6 Least Privilege
  • SI-2 Flaw Remediation
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 7 hardening rules · 4 OS baselines
Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly mitigates the network-exploitable DoS that crashes or hangs the MySQL Optimizer by enforcing denial-of-service protection mechanisms.

prevent

Limits the impact of the low-privileged attacker (CWE-732) by restricting unnecessary privileges that enable the optimizer-based crash.

prevent

Requires timely patching of the affected MySQL versions (8.0.0-9.2.0) to eliminate the optimizer flaw before exploitation.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-05 full match
prevents

Directly requires defining, enforcing, and reviewing access permissions and least privilege on resources.

PR.PS-01 mostly match
prevents

Hardened baselines and configuration management explicitly include correct permission settings for critical resources.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

By requiring owners to determine and document the exact permissions needed for each asset, the control reduces the likelihood that default or overly permissive file and resource permissions will be left in place.

prevents

Documented provisioning and revocation procedures reduce the chance that critical resources retain overly permissive default or leftover permissions after personnel changes.

prevents

Documented authorization, expiry rules, and audit logging of privileged accounts make it harder for critical resources to retain overly permissive or stale permission assignments.

prevents

Requiring explicit configuration of access controls and permissions for files, applications and services counters the assignment of overly permissive default or incorrect file-system rights.

prevents

Enforcing differentiated permissions on the source-code repository and program listings stops the assignment of overly broad default or inherited permissions to critical resources.

prevents

By defining and enforcing secure permission settings in configuration templates, the control reduces the likelihood that critical resources receive incorrect permission assignments.

References