Log integrity compromise via unsanitized user data
Published May 2, 2024 · Updated Feb 13, 2025
Log injection in IBM Cognos Analytics 11.2.0 through 11.2.4 and 12.0.0 through 12.0.2 allows remote attackers to alter application logs. The application logging path writes user-provided data without sanitization; IBM has not identified the specific request field or logging function. Network access without authentication or user interaction is sufficient, and forged log content can support further attacks against the system.
Summary
What happened
Log injection in IBM Cognos Analytics 11.2.0 through 11.2.4 and 12.0.0 through 12.0.2 allows remote attackers to alter application logs. The application logging path writes user-provided data without sanitization; IBM has not identified the specific request field or logging function. Network access without authentication or user interaction is sufficient, and forged log content can support further attacks against the system.
The record
- CVE
- CVE-2024-25047
- Published
- May 2, 2024
- Updated
- Feb 13, 2025
- Vendor
- IBM
- Product
- Cognos Analytics
- Classifications
- CWE-117, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 2, 2024CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=11.2.0, 11.2.1, 11.2.2, 11.2.3, 11.2.4, 12.0.0, 12.0.1, 12.0.2
- Affected versionversion=11.2.0 <= 11.2.4, 12.0.0 <= 12.0.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo