Root code execution via writable core scripts
Published Jan 29, 2020 · Updated Aug 4, 2024
Incorrect permissions in Wowza Streaming Engine 4.8.0 and earlier allow local users to execute code as root on Linux. The installer makes core files under /usr/local/WowzaStreamingEngine/bin writable by unprivileged users, so replacing tune.sh injects code into a root-run server action. Any local account can plant the payload; it executes with root privileges when the server invokes the modified file.
Summary
What happened
Incorrect permissions in Wowza Streaming Engine 4.8.0 and earlier allow local users to execute code as root on Linux. The installer makes core files under /usr/local/WowzaStreamingEngine/bin writable by unprivileged users, so replacing tune.sh injects code into a root-run server action. Any local account can plant the payload; it executes with root privileges when the server invokes the modified file.
The record
- CVE
- CVE-2019-7656
- Published
- Jan 29, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-732, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 29, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- tune.sh replacement privilege-escalation proof of conceptproof of concept · demonstrated
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