CVE-2025-33136
Ibm Aspera Faspex 5.0.0 – 5.0.12.1
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:NSummary
CVE-2025-33136 is a high-severity MAID (CWE-471) vulnerability in Ibm Aspera Faspex. Its CVSS base score is 7.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Path Interception (T1034); ranked at the 24th 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-16173
Vulnerability Data
IBM Aspera Faspex 5.0.0 through 5.0.12 could allow an authenticated user to obtain sensitive information or perform unauthorized actions on behalf of another user due to improper protection of assumed immutable data.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 1 hardening rule · 1 OS baseline
—
Mitigating Controls (NIST 800-53 r5) AI
Access enforcement directly stops unauthorized modification of elements that should remain immutable.
Least privilege reduces the set of subjects that can reach or alter assumed-immutable data.
Integrity verification tools discover unauthorized changes after they occur.
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.
Least-privilege access controls directly block unauthorized writes to assumed-immutable data.
Integrity mechanisms for data-at-rest prevent modification of elements expected to remain immutable.
Protecting data-in-use integrity stops runtime tampering of values treated as constant.
Logical access controls reduce the attack surface for modifying internal assumed-immutable state.
Hardened configuration baselines limit opportunities to alter data presumed immutable.
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 unauthorized modification paths for assumed-immutable data.
Secure SDLC practices include design reviews that identify and protect data assumed to be immutable.
Application security requirements can mandate integrity protections for data declared immutable.
Secure architecture principles call for explicit immutability guarantees and enforcement mechanisms.
Secure coding standards discourage mutable storage for values that must remain constant.
Access-control rules directly prevent unauthorized modification of data assumed to be immutable.
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).
Windows 10 (1 rule)
- V-220812 Credential Guard must be running on Windows 10 domain-joined systems. prevents CWE-471