CVE-2025-60679: A stack buffer overflow vulnerability exists in the D-Link DIR-816A2 router firmware DIR-816A2_FWv1.10CNB05...
A stack buffer overflow vulnerability exists in the D-Link DIR-816A2 router firmware DIR-816A2_FWv1.10CNB05_R1B011D88210.img in the upload.cgi module, which handles firmware version information. The vulnerability occurs because /proc/version is read into a 512-byte buffer and then concatenated using sprintf() into another 512-byte buffer containing a 29-byte constant. Input exceeding 481 bytes triggers a stack buffer overflow, allowing an attacker who can control /proc/version content to potentially execute arbitrary code on the device.
Security readout for executives and security teams
Plain-English summary
CVE-2025-60679 is a high-severity memory corruption issue reported in D-Link DIR-816A2 router firmware. If the vulnerable condition is reachable, an attacker with low privileges could potentially run code on the device. Public evidence does not show active exploitation or a confirmed vendor patch in the provided sources.
Executive priority
Treat this as a high-priority network-edge device risk if DIR-816A2 routers are present. Prioritize inventory, exposure reduction, and vendor confirmation because routers often sit at sensitive trust boundaries and the provided sources do not confirm a patch.
Technical view
The issue is a stack buffer overflow in upload.cgi handling firmware version information. The code reads /proc/version into a 512-byte buffer, then uses sprintf() into another 512-byte buffer with a 29-byte constant. Content above 481 bytes can overflow the stack. CVSS 3.1 is 8.8: network, low complexity, low privileges, no user interaction.
Likely exposure
Likely exposure is limited to environments using the referenced D-Link DIR-816A2 firmware image. The bundle’s structured affected-product fields are empty, so product/version scope should be treated as incomplete until confirmed against D-Link guidance and device inventory.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and no cited source confirms active exploitation. Practical exploitability is also constrained by the stated requirement that an attacker can control /proc/version content, which needs validation in real deployments.
Researcher notes
The report names CWE-121 and describes a fixed-size buffer misuse in upload.cgi. The main evidence gap is reachability: the source says exploitation depends on controlling /proc/version content. Validate affected firmware and attack preconditions carefully before rating local exploitability.
Mitigation direction
Check D-Link’s security bulletin for official affected-version and fix guidance.
Restrict router administration interfaces to trusted management networks only.
Remove affected devices from direct internet exposure where possible.
Replace or retire unsupported DIR-816A2 devices if no vendor fix exists.
Monitor for unexpected firmware, configuration, or administrator account changes.
Validation and detection
Inventory D-Link DIR-816A2 devices and record exact firmware versions.
Compare firmware against the named DIR-816A2_FWv1.10CNB05 image.
Review D-Link advisories for this CVE before remediation decisions.
Confirm management interfaces are not publicly reachable.
Avoid reproducing the overflow on production devices.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-121: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-121 · source CWE mapping
Stack-based Buffer Overflow
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.