Root privilege escalation via writable cron script
Published Apr 15, 2020 · Updated Sep 17, 2024
Incorrect default permissions in QRadar's run-result-reader.sh in IBM QRadar 7.3.0 through 7.3.3 Patch 2 allow local users to gain root privileges. The script is owned by nobody but is launched every 20 minutes from root's crontab, so nobody-context processes can replace its commands. Access as the nobody account is required; modified commands then execute as root and permit full control of the host.
Summary
What happened
Incorrect default permissions in QRadar's run-result-reader.sh in IBM QRadar 7.3.0 through 7.3.3 Patch 2 allow local users to gain root privileges. The script is owned by nobody but is launched every 20 minutes from root's crontab, so nobody-context processes can replace its commands. Access as the nobody account is required; modified commands then execute as root and permit full control of the host.
The record
- CVE
- CVE-2020-4270
- Published
- Apr 15, 2020
- Updated
- Sep 17, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-276, T1574.010
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 15, 2020CVE publishedPublication date reported by the CVE source.
- Sep 17, 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- run-result-reader.sh insecure-permissions exploitfunctional · 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