CVE-2026-7853
Buffer Overflow in D-Link DI-8100 Router Firmware
Publication date: 2026-05-05
Last updated on: 2026-05-06
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| dlink | di-8100_firmware | 16.07.26a1 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-119 | The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data. |
| CWE-120 | The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a critical stack-based buffer overflow in the D-Link DI-8100 router firmware version 16.07.26A1, specifically in the /auto_reboot.asp endpoint handled by the HTTP daemon (jhttpd).
The flaw occurs due to unsafe use of the sprintf() function when processing user-controlled parameters 'enable' and 'time' retrieved from NVRAM. These parameters are copied into a fixed-size stack buffer of 104 bytes without proper length validation.
An unauthenticated remote attacker can exploit this by sending a specially crafted HTTP POST request with overly long values for these parameters, causing memory corruption that can overwrite the return address and hijack the execution flow.
This can lead to the HTTP daemon crashing or potentially allow the attacker to execute arbitrary code on the router.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability in the D-Link DI-8100 router allows unauthenticated remote attackers to potentially execute arbitrary code, leading to full router compromise. This could result in exposure of sensitive data, tampering with configurations, or denial of service.
Such a compromise could negatively impact compliance with common standards and regulations like GDPR and HIPAA, which require protection of sensitive data and maintaining system integrity and availability.
However, the provided information does not explicitly discuss compliance implications or specific regulatory impacts.
How can this vulnerability impact me? :
Exploitation of this vulnerability can have severe impacts including full compromise of the affected router.
- An attacker can crash the HTTP daemon, causing denial of service.
- The attacker may execute arbitrary code, potentially gaining control over the router.
- Sensitive data stored on the router could be exposed.
- Router configurations could be tampered with, affecting network security and stability.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring for unusual or malformed HTTP POST requests targeting the /auto_reboot.asp endpoint of the D-Link DI-8100 router firmware version 16.07.26A1.
Specifically, detection involves identifying POST requests with overly long or suspiciously large values in the enable and time parameters, which are used to trigger the buffer overflow.
Network administrators can use packet capture tools like tcpdump or Wireshark to filter and inspect HTTP POST traffic to the /auto_reboot.asp endpoint.
- Use tcpdump to capture HTTP POST requests to /auto_reboot.asp: tcpdump -i <interface> -A 'tcp port 80 and (((ip[2:2] - ((ip[0]&0xf)<<2)) - ((tcp[12]&0xf0)>>2)) != 0)' | grep 'POST /auto_reboot.asp'
- Use curl or similar tools to test the endpoint with large payloads for enable and time parameters to verify if the system is vulnerable.
- Check router logs for crashes or restarts of the HTTP daemon (jhttpd), which may indicate exploitation attempts.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the /auto_reboot.asp endpoint to trusted networks or IP addresses to prevent remote exploitation.
Implement network-level filtering or firewall rules to block suspicious HTTP POST requests with unusually large enable and time parameters.
Monitor the router for signs of compromise such as unexpected crashes or configuration changes.
If possible, update the router firmware to a version that patches this vulnerability or apply any available vendor-provided security updates.
As a temporary workaround, disable remote management features or restrict administrative access until a patch is applied.