Container compromise via pod-access system calls
Published May 29, 2024 · Updated Aug 2, 2024
Privilege escalation in IBM Db2 on Cloud Pak for Data 3.5, 4.0, 4.5, 4.6, 4.7, and 4.8 allows local users to compromise containers. The Db2U Kubernetes pod permits security-sensitive system calls from a user who already has pod access; IBM has not disclosed the responsible code path or missing restriction. Exploitation requires access inside a Kubernetes pod and can undermine container confidentiality, integrity, and availability, without a reported remote service vector.
Summary
What happened
Privilege escalation in IBM Db2 on Cloud Pak for Data 3.5, 4.0, 4.5, 4.6, 4.7, and 4.8 allows local users to compromise containers. The Db2U Kubernetes pod permits security-sensitive system calls from a user who already has pod access; IBM has not disclosed the responsible code path or missing restriction. Exploitation requires access inside a Kubernetes pod and can undermine container confidentiality, integrity, and availability, without a reported remote service vector.
The record
- CVE
- CVE-2023-42005
- Published
- May 29, 2024
- Updated
- Aug 2, 2024
- Vendor
- IBM
- Product
- Db2 on IBM Cloud Pak for Data
- Classifications
- CWE-264, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 29, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record 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=3.5, 4.0, 4.5, 4.6, 4.7, 4.8
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