CVE-2025-36228
Ibm Aspera Faspex 5.0.0 – 5.0.14.2
Raw vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:NSummary
CVE-2025-36228 is a low-severity Incorrect Execution-Assigned Permissions (CWE-279) vulnerability in Ibm Aspera Faspex. Its CVSS base score is 3.8 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique File and Directory Permissions Modification (T1222); ranked at the 11th 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-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-205441
Vulnerability Data
IBM Aspera Faspex 5 5.0.0 through 5.0.14.1 may allow inconsistent permissions between the user interface and backend API allowed users to access features that appeared disabled, potentially leading to misuse.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 2 hardening rules · 1 OS baseline
—
Mitigating Controls (NIST 800-53 r5) AI
Enforcing approved authorizations structurally stops the runtime assignment of permissions that violate user intent.
Requiring least privilege limits the permissions the executing code is allowed to assign.
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.
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.
Restricting privileged utility programs reduces the chance that such tools will incorrectly alter object permissions.
Privileged access rights management directly constrains the permissions a process may assign at runtime.
Secure coding practices can prevent the coding error that leads to incorrect permission assignment.
Information access restriction policies limit the permissions that executing code can grant or modify.
Change-management procedures can catch permission-setting mistakes before they reach production.