Administrator takeover via forged cli.cgi requests
Published Feb 4, 2020 · Updated Aug 6, 2024
Cross-site request forgery in D-Link DIR-100 firmware 4.03B07 and earlier allows remote attackers to alter router configuration. The cli.cgi handler accepts command-bearing GET requests from the IP address of an active administrator session without validating a session token or request origin. A logged-in administrator must load the crafted request; it can change the administrator password and enable remote management.
Summary
What happened
Cross-site request forgery in D-Link DIR-100 firmware 4.03B07 and earlier allows remote attackers to alter router configuration. The cli.cgi handler accepts command-bearing GET requests from the IP address of an active administrator session without validating a session token or request origin. A logged-in administrator must load the crafted request; it can change the administrator password and enable remote management.
The record
- CVE
- CVE-2013-7053
- Published
- Feb 4, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-352, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 4, 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 DIR-100 Multiple Vulnerabilitiesproof 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