CVE Vulnerabilities

CVE-2025-7493

Insufficient Granularity of Access Control

Published: Sep 30, 2025 | Modified: Oct 09, 2025
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
RedHat/V2
RedHat/V3
9.1 IMPORTANT
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Ubuntu
MEDIUM

A privilege escalation flaw from host to domain administrator was found in FreeIPA. This vulnerability is similar to CVE-2025-4404, where it fails to validate the uniqueness of the krbCanonicalName. While the previously released version added validations for the admin@REALM credential, FreeIPA still does not validate the root@REALM canonical name, which can also be used as the realm administrators name. This flaw allows an attacker to perform administrative tasks over the REALM, leading to access to sensitive data and sensitive data exfiltration.

Weakness

The product implements access controls via a policy or other feature with the intention to disable or restrict accesses (reads and/or writes) to assets in a system from untrusted agents. However, implemented access controls lack required granularity, which renders the control policy too broad because it allows accesses from unauthorized agents to the security-sensitive assets.

Affected Software

Name Vendor Start Version End Version
Red Hat Enterprise Linux 10 RedHat ipa-0:4.12.2-15.el10_0.4 *
Red Hat Enterprise Linux 8 RedHat idm:client-8100020250919180242.143e9e98 *
Red Hat Enterprise Linux 8 RedHat idm:DL1-8100020250918211722.823393f5 *
Red Hat Enterprise Linux 9 RedHat ipa-0:4.12.2-14.el9_6.5 *
Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions RedHat ipa-0:4.9.8-11.el9_0.5 *
Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions RedHat ipa-0:4.10.1-12.el9_2.6 *
Red Hat Enterprise Linux 9.4 Extended Update Support RedHat ipa-0:4.11.0-15.el9_4.7 *

Extended Description

Integrated circuits and hardware engines can expose accesses to assets (device configuration, keys, etc.) to trusted firmware or a software module (commonly set by BIOS/bootloader). This access is typically access-controlled. Upon a power reset, the hardware or system usually starts with default values in registers, and the trusted firmware (Boot firmware) configures the necessary access-control protection. A common weakness that can exist in such protection schemes is that access controls or policies are not granular enough. This condition allows agents beyond trusted agents to access assets and could lead to a loss of functionality or the ability to set up the device securely. This further results in security risks from leaked, sensitive, key material to modification of device configuration.

Potential Mitigations

References