Persistent root access via CLI password overwrite
Published Feb 19, 2020 · Updated Aug 6, 2024
Missing authorization in D-Link DSR-250N firmware before 1.08B31 allows remote authenticated users to gain persistent root access via the BusyBox CLI. The CLI exposes commands that overwrite the super user password without restricting their use to an appropriately privileged account. Access to the authenticated CLI is required, and successful exploitation grants durable root control over the router.
Summary
What happened
Missing authorization in D-Link DSR-250N firmware before 1.08B31 allows remote authenticated users to gain persistent root access via the BusyBox CLI. The CLI exposes commands that overwrite the super user password without restricting their use to an appropriately privileged account. Access to the authenticated CLI is required, and successful exploitation grants durable root control over the router.
The record
- CVE
- CVE-2012-6614
- Published
- Feb 19, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-862, T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 19, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 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.
Public exploit references
- D-Link DSR-250N Backdoorfunctional · 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