Root code execution via sourced writable script
Published Mar 3, 2020 · Updated Sep 16, 2024
Code injection in pcp packaging on affected SUSE and openSUSE releases allows local users with pcp access to execute code as root. The privileged package-update script sources /var/log/pcp/configs.sh even though the pcp account can place shell content at that path. Control of the pcp account and a subsequent package update are required; injected shell commands then run with root privileges.
Summary
What happened
Code injection in pcp packaging on affected SUSE and openSUSE releases allows local users with pcp access to execute code as root. The privileged package-update script sources /var/log/pcp/configs.sh even though the pcp account can place shell content at that path. Control of the pcp account and a subsequent package update are required; injected shell commands then run with root privileges.
The record
- CVE
- CVE-2019-3695
- Published
- Mar 3, 2020
- Updated
- Sep 16, 2024
- Vendor
- OpenSUSE
- Product
- openSUSE Leap
- Classifications
- CWE-94, T1059.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 3, 2020CVE 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=pcp <4.3.1-lp151.2.3.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