CVE-2025-60686: A local stack-based buffer overflow vulnerability exists in the infostat.cgi and cstecgi.cgi binaries of To...
A local stack-based buffer overflow vulnerability exists in the infostat.cgi and cstecgi.cgi binaries of ToToLink routers (A720R V4.1.5cu.614_B20230630, LR1200GB V9.1.0u.6619_B20230130, and NR1800X V9.1.0u.6681_B20230703). Both programs parse the contents of /proc/net/arp using sscanf() with "%s" format specifiers into fixed-size stack buffers without length validation. Specifically, one function writes user-controlled data into a single-byte buffer, and the other into adjacent small arrays without bounds checking. An attacker who controls the contents of /proc/net/arp can trigger memory corruption, leading to denial of service or potential arbitrary code execution.
Security readout for executives and security teams
Plain-English summary
CVE-2025-60686 is a local memory-corruption flaw in specific ToToLink router firmware. A process reads ARP table data into undersized stack buffers. If an attacker can control that input, the router process may crash, and code execution is considered possible but not proven in the provided sources.
Executive priority
Treat this as a moderate infrastructure risk. It is not currently supported as actively exploited, but affected routers are security boundary devices. Remediate during normal vulnerability cycles, faster where untrusted local users share the network.
Technical view
The issue affects infostat.cgi and cstecgi.cgi on named ToToLink A720R, LR1200GB, and NR1800X firmware versions. Both parse /proc/net/arp with unbounded sscanf("%s") into fixed-size stack buffers, including a single-byte buffer and adjacent small arrays, causing stack-based overflow risk.
Likely exposure
Exposure appears limited to ToToLink A720R V4.1.5cu.614_B20230630, LR1200GB V9.1.0u.6619_B20230130, and NR1800X V9.1.0u.6681_B20230703 devices. The CVE record’s structured affected fields are incomplete, so confirm models and firmware directly.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation. The attack is rated local and depends on controlling /proc/net/arp contents. Public researcher material exists, but the provided evidence does not establish exploitation in the wild.
Researcher notes
Evidence is strongest for the unsafe parsing pattern and named firmware builds. Patch status, vendor acknowledgement, and complete CPE metadata are not established in the provided bundle. Avoid assuming broader ToToLink impact without firmware confirmation.
Mitigation direction
Check ToToLink guidance for updated firmware or replacement direction.
Inventory routers and prioritize named firmware versions for remediation.
Restrict local and administrative access to affected routers.
Segment untrusted clients away from affected network devices.
Monitor affected routers for unexpected CGI crashes or reboots.
Validation and detection
Confirm router model and exact firmware build against the CVE description.
Review ToToLink support channels for firmware or advisory updates.
Check whether infostat.cgi or cstecgi.cgi exist on deployed images.
Correlate device logs for abnormal CGI failures or availability events.
Track the CVE record for corrected affected-product metadata.
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
3Source 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.