Security Resilience

CVE-2024-27264

LPE in Ibm I 7.2 … 7.5

Published
22 May 2024
Modified
30 June 2025
Patch / advisory
CVSS Score v3.1 7.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0014 3th percentile
Risk Priority 51 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-27264 is a high-severity Improper Privilege Management (CWE-269) vulnerability in Ibm I. Its CVSS base score is 7.4 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Services File Permissions Weakness (T1574.010); ranked at the 3th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-2 (Account Management) and AC-24 (Access Control Decisions) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

IBM Performance Tools for i 7.2, 7.3, 7.4, and 7.5 could allow a local user to gain elevated privileges due to an unqualified library call. A malicious actor could cause user-controlled code to run with administrator privilege. IBM X-Force ID:…

more

284563.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1574.010 Services File Permissions Weakness Stealth
Adversaries may execute their own malicious payloads by hijacking the binaries used by services.
T1003.001 LSASS Memory Credential Access
Adversaries may attempt to access credential material stored in the process memory of the Local Security Authority Subsystem Service (LSASS).
T1003.006 DCSync Credential Access
Adversaries may attempt to access credentials and other sensitive information by abusing a Windows Domain Controller's application programming interface (API)(Citation: Microsoft DRSR Dec 2017) (Citation: Microsoft GetNCCChanges) (Citati…
T1010 Application Window Discovery Discovery
Adversaries may attempt to get a listing of open application windows.
T1011.001 Exfiltration Over Bluetooth Exfiltration
Adversaries may attempt to exfiltrate data over Bluetooth rather than the command and control channel.
T1021.002 SMB/Windows Admin Shares Lateral Movement
Adversaries may use [Valid Accounts](https://attack.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-2311Same product: Ibm I
CVE-2024-35139Same vendor: Ibm
CVE-2023-38370Same vendor: Ibm
CVE-2024-46916Shared CWE-269, CWE-276
CVE-2023-50300Same vendor: Ibm
CVE-2023-32333Same vendor: Ibm
CVE-2026-0977Same vendor: Ibm
CVE-2023-38263Same vendor: Ibm
CVE-2023-40363Same vendor: Ibm
CVE-2025-36351Same vendor: Ibm

Affected Assets

ibm
i
7.2, 7.3, 7.4, 7.5

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

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

—

Mitigating Controls (NIST 800-53 r5) AI

Directly enforces approved authorizations for logical access, stopping unauthorized actors from reaching resources.

Account management directly governs assignment and tracking of privileges so proper implementation stops the weakness from being introduced.

Requiring explicit access-control decisions ensures privileges are evaluated rather than assumed or omitted.

Enforces flow-control policies that restrict information movement between subjects and objects.

Separation of duties constrains how privileges may be assigned, reducing the chance of overly broad actor control.

Least privilege is the direct countermeasure to improper privilege management; implementing it eliminates the root cause.

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.

ID.AM-08 partial match
blocks

Lifecycle management can encompass permission settings, yet the control is too broad to specifically mitigate incorrect defaults.

PR.AA-05 partial match
blocks

Defining and enforcing least-privilege access permissions directly prevents overly permissive defaults at install time.

PR.PS-01 partial match
blocks

Hardened baselines and configuration management explicitly require correct default file permissions.

PR.PS-06 partial match
blocks

Secure SDLC practices include establishing secure defaults, but address only the development-phase portion of the weakness.

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.

blocks

A.5.1 only requires that an information security policy and topic-specific policies (including on access control) exist and are reviewed; it does not itself enforce, implement or act on any access restriction, so the weakness can still be exploited (per the owner's explicit rule that governance/dependency clauses score none on effect verbs).

removes
blocks

A.5.15 directly mandates determining access requirements, defining/enforcing topic-specific access control policy, assigning rights/restrictions by entity/role, consistency with classification, need-to-know, privileged access restrictions, segregation, formal authorization, and dynamic rules — which stops most improper privilege management from being exploitable; bounded remainder is flawed implementation of those rules (e.g. incorrect mapping or enforcement bugs).

removes
blocks

A.5.18 directly governs the provisioning, review, modification and timely revocation of access rights (including for role changes, termination and privilege levels), which stops most improper privilege spheres from being exploitable even if the assignment flaw exists; the bounded remainder is flaws in the underlying enforcement mechanism itself (e.g. AC-3/A.8.3)

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (higher-evidence rows only; rows rated `none` are excluded).

Windows Server 2016 (2 rules)
  • V-224833 Permissions for program file directories must conform to minimum requirements. blocks CWE-276
  • V-224834 Permissions for the Windows installation directory must conform to minimum requirements. blocks CWE-276
Windows Server 2019 (2 rules)
  • V-205735 Windows Server 2019 permissions for program file directories must conform to minimum requirements. blocks CWE-276
  • V-205736 Windows Server 2019 permissions for the Windows installation directory must conform to minimum requirements. blocks CWE-276

References