Local file disclosure via privileged post-install operations
Published Oct 16, 2024 · Updated Mar 19, 2025
Insecure file operations in openSUSE Tumbleweed mlocate before 0.26-37.1 allow local users to make arbitrary files world readable. The mlocate %post script performs root-privileged permission changes on paths influenced by the RUN_UPDATEDB_AS account without securely binding operations to intended files. A local user able to act as RUN_UPDATEDB_AS can redirect those operations to disclose file contents otherwise protected by Unix permissions.
Summary
What happened
Insecure file operations in openSUSE Tumbleweed mlocate before 0.26-37.1 allow local users to make arbitrary files world readable. The mlocate %post script performs root-privileged permission changes on paths influenced by the RUN_UPDATEDB_AS account without securely binding operations to intended files. A local user able to act as RUN_UPDATEDB_AS can redirect those operations to disclose file contents otherwise protected by Unix permissions.
The record
- CVE
- CVE-2023-32190
- Published
- Oct 16, 2024
- Updated
- Mar 19, 2025
- Vendor
- OpenSUSE
- Product
- openSUSE Tumbleweed
- Classifications
- CWE-125, T1222.002
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 16, 2024CVE publishedPublication date reported by the CVE source.
- Mar 19, 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=0 <0.26-37.1
- Affected versionversion=? <0.26-37.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