9.8 CVE-2024-45694
The web service of certain models of D-Link wireless routers contains a Stack-based Buffer Overflow vulnerability, which allows unauthenticated remote attackers to exploit this vulnerability to execute arbitrary code on the device.
https://nvd.nist.gov/vuln/detail/CVE-2024-45694
Categories
CWE-121 : Stack-based Buffer Overflow
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). "Stack Overflow" is often used to mean the same thing as stack-based buffer overflow, however it is also used on occasion to mean stack exhaustion, usually a result from an excessively recursive function call. Due to the ambiguity of the term, use of stack overflow to describe either circumstance is discouraged. Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues. Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.) Use an abstraction library to abstract away risky APIs. Not a complete solution. Implement and perform bounds checking on input. Do not use dangerous functions such as gets. Use safer, equivalent functions which check for boundary errors. Stack-based buffer overflows in SFK for wifi chipset used for IoT/embedded devices, as exploited in the wild per CISA KEV.
References
twcert@cert.org.tw
| https://www.twcert.org.tw/en/cp-139-8081-3fb39-2.html Third Party Advisory |
| https://www.twcert.org.tw/tw/cp-132-8080-7f494-1.html Third Party Advisory |
CPE
| cpe | start | end |
|---|---|---|
| Configuration 1 | ||
| AND | ||
| cpe:2.3:o:dlink:dir-x5460_firmware:1.01:*:*:*:*:*:*:* | ||
| cpe:2.3:o:dlink:dir-x5460_firmware:1.02:*:*:*:*:*:*:* | ||
| cpe:2.3:o:dlink:dir-x5460_firmware:1.04:*:*:*:*:*:*:* | ||
| cpe:2.3:o:dlink:dir-x5460_firmware:1.10:*:*:*:*:*:*:* | ||
| Running on/with | ||
| cpe:2.3:h:dlink:dir-x5460:a1:*:*:*:*:*:*:* | ||
| Configuration 2 | ||
| AND | ||
| cpe:2.3:o:dlink:dir-x4860_firmware:1.00:*:*:*:*:*:*:* | ||
| cpe:2.3:o:dlink:dir-x4860_firmware:1.04:*:*:*:*:*:*:* | ||
| Running on/with | ||
| cpe:2.3:h:dlink:dir-x4860:a1:*:*:*:*:*:*:* | ||
REMEDIATION
EXPLOITS
Exploit-db.com
| id | description | date | |
|---|---|---|---|
| No known exploits | |||
POC Github
| Url |
|---|
| No known exploits |
Other Nist (github, ...)
| Url |
|---|
| No known exploits |
CAPEC
Common Attack Pattern Enumerations and Classifications
| id | description | severity |
|---|---|---|
| No entry | ||
Cybersecurity needs ?
Strengthen software security from the outset with our DevSecOps expertise
Integrate security right from the start of the software development cycle for more robust applications and greater customer confidence.
Our team of DevSecOps experts can help you secure your APIs, data pipelines, CI/CD chains, Docker containers and Kubernetes deployments.
