CVE Vulnerabilities

CVE-2025-30703

Incorrect Authorization

Published: Apr 15, 2025 | Modified: Apr 21, 2025
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
RedHat/V2
RedHat/V3
2.7 LOW
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N
Ubuntu
MEDIUM

Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB). 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 high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of MySQL Server accessible data. CVSS 3.1 Base Score 2.7 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N).

Weakness

The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

Affected Software

Name Vendor Start Version End Version
Mysql_server Oracle 8.0.0 (including) 8.0.41 (including)
Mysql_server Oracle 8.4.0 (including) 8.4.4 (including)
Mysql_server Oracle 9.0.0 (including) 9.2.0 (including)
Red Hat Enterprise Linux 10 RedHat mysql8.4-0:8.4.6-2.el10_0 *
Red Hat Enterprise Linux 10 RedHat mysql-selinux-0:1.0.14-1.el10_0 *
Red Hat Enterprise Linux 9 RedHat mysql:8.4-9060020250910121712.rhel9 *
Red Hat Enterprise Linux 9 RedHat mysql-0:8.0.43-1.el9_6 *
Mariadb Ubuntu oracular *
Mariadb-10.3 Ubuntu esm-apps/focal *
Mariadb-10.3 Ubuntu focal *
Mysql-5.5 Ubuntu esm-infra-legacy/trusty *
Mysql-5.7 Ubuntu esm-infra/bionic *
Mysql-5.7 Ubuntu esm-infra/xenial *
Mysql-8.0 Ubuntu esm-infra/focal *
Mysql-8.0 Ubuntu focal *
Mysql-8.0 Ubuntu jammy *
Mysql-8.0 Ubuntu noble *
Mysql-8.0 Ubuntu oracular *
Mysql-8.0 Ubuntu upstream *
Mysql-8.4 Ubuntu devel *
Mysql-8.4 Ubuntu plucky *
Mysql-8.4 Ubuntu upstream *

Potential Mitigations

  • Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries.
  • Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
  • For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page.
  • One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.

References