TP-Link TL-WDR7660 1.0 guestRuleJsonToBin string name stack-based overflow

Summaryinfo

A vulnerability classified as critical has been found in TP-Link TL-WDR7660 1.0. The affected element is the function guestRuleJsonToBin. The manipulation of the argument string name leads to stack-based overflow. This vulnerability is uniquely identified as CVE-2024-48714. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in TP-Link TL-WDR7660 1.0 and classified as critical. This issue affects the function guestRuleJsonToBin. The manipulation of the argument string name with an unknown input leads to a stack-based overflow vulnerability. Using CWE to declare the problem leads to CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). Impacted is confidentiality, integrity, and availability. The summary by CVE is:

In TP-Link TL-WDR7660 v1.0, the guestRuleJsonToBin function handles the parameter string name without checking it, which can lead to stack overflow vulnerabilities.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2024-48714 since 10/08/2024. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/16/2024).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Router Operating System

Vendor

• TP-Link

Name

• TL-WDR7660

Version

• 1.0

License

• commercial

Website

• Vendor: https://www.tp-link.com/

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion