Audit-record integrity loss
Published Jul 9, 2023 · Updated Feb 13, 2025
Insufficient audit logging in IBM Db2 11.1.4.7 and 11.5.x allows remote authenticated users to compromise audit-record integrity. IBM has not published which Db2 operation is omitted from the audit trail or how audit records become incomplete. Low-privileged network access is required, and no confidentiality or availability consequence is reported.
Summary
What happened
Insufficient audit logging in IBM Db2 11.1.4.7 and 11.5.x allows remote authenticated users to compromise audit-record integrity. IBM has not published which Db2 operation is omitted from the audit trail or how audit records become incomplete. Low-privileged network access is required, and no confidentiality or availability consequence is reported.
The record
- CVE
- CVE-2023-23487
- Published
- Jul 9, 2023
- Updated
- Feb 13, 2025
- Vendor
- IBM
- Product
- IBM Db2 for Linux, UNIX, and Windows
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 9, 2023CVE 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.1 ,11.5
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
No sourced classifications are available.
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