Local file tampering via incorrect DEB ownership
Published Oct 7, 2021 · Updated Aug 3, 2024
Improper access control in Apache OpenOffice 4.1.8 DEB packages allows local users assigned ID 500 to modify installed files. The packages record user and group ID 500 instead of root ownership, so installation assigns OpenOffice files to any preexisting account or group with those numeric IDs. Exploitation requires a Linux DEB installation and a local account or group mapped to ID 500; affected principals can tamper with files that the package wrongly places under their ownership.
Summary
What happened
Improper access control in Apache OpenOffice 4.1.8 DEB packages allows local users assigned ID 500 to modify installed files. The packages record user and group ID 500 instead of root ownership, so installation assigns OpenOffice files to any preexisting account or group with those numeric IDs. Exploitation requires a Linux DEB installation and a local account or group mapped to ID 500; affected principals can tamper with files that the package wrongly places under their ownership.
The record
- CVE
- CVE-2021-28129
- Published
- Oct 7, 2021
- Updated
- Aug 3, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache OpenOffice
- Classifications
- CWE-284
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 7, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=Apache OpenOffice 4.1.8
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