CVE-2025-36251
Ibm Vios 3.1.0 … 4.1.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:LSummary
CVE-2025-36251 is a critical-severity Process Control (CWE-114) vulnerability in Ibm Vios. Its CVSS base score is 9.6 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Shared Modules (T1129); ranked at the 43th 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 CM-7 (Least Functionality) and SC-18 (Mobile Code) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-36251 is a high-severity vulnerability in the nimsh service SSL/TLS implementations on IBM AIX 7.2 and 7.3, as well as IBM VIOS 3.1 and 4.1. It arises from improper process controls (CWE-114), enabling a remote attacker to execute arbitrary commands. Published on 2025-11-13, this issue addresses additional attack vectors related to a vulnerability previously fixed in CVE-2024-56347. The CVSS v3.1 base score is 9.6 (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:L).
A remote attacker can exploit this over the network with low attack complexity and no privileges required, though user interaction is necessary. Upon successful exploitation, the attacker achieves high confidentiality and integrity impacts, such as accessing sensitive data or modifying system behavior through arbitrary command execution, alongside low availability impact and a crossed scope that affects additional privileges or components.
IBM's security advisory at https://www.ibm.com/support/pages/node/7251173 details the vulnerability, affected versions, and recommended mitigation steps, including available patches.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-180541
Vulnerability Data
IBM AIX 7.2, and 7.3 and IBM VIOS 3.1, and 4.1 nimsh service SSL/TLS implementations could allow a remote attacker to execute arbitrary commands due to improper process controls. This addresses additional attack vectors for a vulnerability that was previously…
more
addressed in CVE-2024-56347.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 8 hardening rules · 6 OS baselines
—
Mitigating Controls (NIST 800-53 r5) AI
Least functionality directly restricts execution of commands or loading of libraries to only approved capabilities, stopping untrusted sources from being used.
Mobile code control explicitly defines and enforces acceptable sources and technologies for code/commands loaded at runtime.
Malicious code protection mechanisms block execution or loading of code from untrusted sources before it can run.
Policies and enforcement for user-installed software prevent introduction and execution of untrusted libraries or commands.
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.
Explicitly prevents execution of unauthorized software, directly blocking untrusted commands or libraries.
Assessing authenticity/integrity before acquisition reduces use of untrusted sources for commands/libraries.
Hardened configuration baselines can enforce trusted paths and execution policies.
Secure SDLC practices can embed checks against dynamic loading from untrusted sources.
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.
Security testing can detect unsafe process or library loading but does not prevent it by itself.
Restricting software installation prevents loading untrusted libraries or executing commands from unknown sources.
Secure development lifecycle practices include controls on external code and command execution paths.
Application security requirements can mandate validation of external inputs and libraries.
Secure architecture principles discourage reliance on untrusted external processes or libraries.
Secure coding standards explicitly forbid executing or loading code from untrusted sources.
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` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (3 rules)
- V-248568 OL 8 system commands must be owned by root. prevents CWE-114
- V-248567 OL 8 system commands must have mode 755 or less permissive. prevents CWE-114
- V-248569 OL 8 system commands must be group-owned by root or a system account. prevents CWE-114
Windows 10 (1 rule)
- V-220828 The default autorun behavior must be configured to prevent autorun commands. prevents CWE-114
Windows 11 (1 rule)
- V-253387 The default autorun behavior must be configured to prevent autorun commands. prevents CWE-114
Windows Server 2016 (1 rule)
- V-224933 The default AutoRun behavior must be configured to prevent AutoRun commands. prevents CWE-114
Windows Server 2019 (1 rule)
- V-205805 Windows Server 2019 default AutoRun behavior must be configured to prevent AutoRun commands. prevents CWE-114
Windows Server 2022 (1 rule)
- V-254353 Windows Server 2022 default AutoRun behavior must be configured to prevent AutoRun commands. prevents CWE-114