Local audit logging bypass
Published Apr 9, 2021 · Updated Sep 16, 2024
Audit logging bypass in IBM Spectrum Scale 5.1.0.1 allows local users to prevent file activity from being recorded when FAL is enabled. IBM identifies the locus only as the file audit logging mechanism and has not published the faulty operation or triggering file action. Local access and enabled file audit logging are required; exploitation removes expected audit evidence without affecting confidentiality or availability.
Summary
What happened
Audit logging bypass in IBM Spectrum Scale 5.1.0.1 allows local users to prevent file activity from being recorded when FAL is enabled. IBM identifies the locus only as the file audit logging mechanism and has not published the faulty operation or triggering file action. Local access and enabled file audit logging are required; exploitation removes expected audit evidence without affecting confidentiality or availability.
The record
- CVE
- CVE-2021-29671
- Published
- Apr 9, 2021
- Updated
- Sep 16, 2024
- Vendor
- IBM
- Product
- IBM Spectrum Scale
- Classifications
- T1562
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 9, 2021CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=5.1.0.1
What conditions does exploitation require?
What is affected?
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