CVE-2025-33111
Ibm Cognos Controller 11.0.0 – 11.0.1.7
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NSummary
CVE-2025-33111 is a medium-severity Creation of Temporary File in Directory with Insecure Permissions (CWE-379) vulnerability in Ibm Cognos Controller. Its CVSS base score is 4.3 (Medium).
Operationally, ranked at the 9th 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 SC-4 (Information in Shared System Resources) and AC-6 (Least Privilege) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-201818
Vulnerability Data
IBM Controller 11.1.0 through 11.1.1 and IBM Cognos Controller 11.0.0 through 11.0.1 FP6 is vulnerable to creation of temporary files without atomic operations which may expose sensitive information to an authenticated user due to race condition attacks.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly prevents unintended information exposure through shared resources such as non-atomically created temporary files.
Limits authenticated user privileges so they cannot exploit the race condition to read another user's temporary files.
Maintains separate execution domains that reduce the ability of one process to interfere with another's temporary-file operations.
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.
Secure SDLC practices directly prevent developers from writing code that creates temp files in insecure directories.
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.
Secure system architecture principles include proper file-system permission models that mitigate insecure temp-file creation.
Secure coding standards directly require safe temporary-file creation with restrictive permissions.
Information access restriction policies can limit who may read or list files in shared temporary directories.
Configuration management can enforce secure default permissions on temporary directories.