CVE-2023-48194: Vulnerability in Tenda AC8v4 .V16.03.34.09 due to sscanf and the last digit of s8 being overwritten with \x0.
Vulnerability in Tenda AC8v4 .V16.03.34.09 due to sscanf and the last digit of s8 being overwritten with \x0. After executing set_client_qos, control over the gp register can be obtained.
Security readout for executives and security teams
Plain-English summary
This is a memory corruption flaw reported in Tenda AC8v4 firmware V16.03.34.09. An attacker on an adjacent network may be able to affect confidentiality, integrity, and availability at a limited level. The provided sources do not confirm active exploitation or a vendor-fixed version.
Executive priority
Handle as a targeted network-appliance risk, not an internet-wide emergency based on the provided evidence. Prioritize affected routers in shared, guest, branch, or unmanaged Wi-Fi environments.
Technical view
The CVE describes a CWE-787 out-of-bounds write related to sscanf handling in set_client_qos, where part of s8 is overwritten with a null byte. The report states this can lead to control over the gp register. CVSS 3.1 is 6.3 with adjacent-network attack vector and no privileges required.
Likely exposure
Exposure appears limited to environments running Tenda AC8v4 firmware V16.03.34.09 where an adjacent network attacker can reach the vulnerable functionality. The CVE affected-product metadata is incomplete, so inventory confirmation is essential.
Exploitation context
The bundle includes a public GitHub reference, but it does not establish active exploitation. The CVE is not listed as KEV in the provided data. Treat exploitability as plausible but not confirmed in-the-wild.
Researcher notes
The CVE record lacks structured affected CPEs and does not name a fixed release. Analysis should stay anchored to AC8v4 V16.03.34.09 and avoid extrapolating to other Tenda models without vendor confirmation.
Mitigation direction
Inventory Tenda AC8v4 devices and identify firmware version V16.03.34.09.
Check Tenda guidance and downloads for firmware updates or replacement advice.
Restrict untrusted adjacent-network access to router management and device-control surfaces.
Segment guest, IoT, and unmanaged networks away from affected devices.
Monitor router logs and configuration changes for unexpected QoS-related activity.
Validation and detection
Confirm device model and firmware version from router administration or asset records.
Verify whether vulnerable devices are reachable from guest, Wi-Fi, or adjacent network segments.
Review Tenda download guidance for newer firmware applicable to AC8v4.
Check whether QoS/client-control functionality is exposed to untrusted local users.
Document compensating controls where no vendor fix is confirmed.
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-787: 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.
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.
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-787 · source CWE mapping
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.