Root command execution via firmware update race
Published Jan 27, 2020 · Updated Sep 17, 2024
Command execution in Bitdefender BOX 2 before 2.1.47.36 allows remote attackers on its setup network to run commands as root. The update_setup_async path releases its request lock before image validation and unpacking finish, allowing a second upload to replace the checked archive in /tmp. Exploitation requires access to the appliance setup network and carefully timed uploads, after which an attacker-controlled preinst script runs as root.
Summary
What happened
Command execution in Bitdefender BOX 2 before 2.1.47.36 allows remote attackers on its setup network to run commands as root. The update_setup_async path releases its request lock before image validation and unpacking finish, allowing a second upload to replace the checked archive in /tmp. Exploitation requires access to the appliance setup network and carefully timed uploads, after which an attacker-controlled preinst script runs as root.
The record
- CVE
- CVE-2019-17102
- Published
- Jan 27, 2020
- Updated
- Sep 17, 2024
- Vendor
- Bitdefender
- Product
- Bitdefender BOX 2
- Classifications
- CWE-413, CWE-367, T1190
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 27, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <2.1.47.36
What conditions does exploitation require?
What is affected?
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
- Cisco Talos TALOS-2019-0918 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