libcoap Stack-Based Buffer Overflow in Address Resolution DoS or Potential RCE
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| libcoap | libcoap | unaffected |
|
No data.
| Vendor | Product | Versions |
|---|---|---|
| Libcoap | Libcoap | — |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.748% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-787 | |
| CPEs | cpe:2.3:a:libcoap:libcoap:*:*:*:*:*:*:*:* | |
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Libcoap
Libcoap libcoap |
|
| Vendors & Products |
Libcoap
Libcoap libcoap |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | libcoap versions up to and including 4.3.5, prior to commit 30db3ea, contain a stack-based buffer overflow in address resolution when attacker-controlled hostname data is copied into a fixed 256-byte stack buffer without proper bounds checking. A remote attacker can trigger a crash and potentially achieve remote code execution depending on compiler options and runtime memory protections. Exploitation requires the proxy logic to be enabled (i.e., the proxy request handling code path in an application using libcoap). | |
| Title | libcoap Stack-Based Buffer Overflow in Address Resolution DoS or Potential RCE | |
| Weaknesses | CWE-121 | |
| References |
| |
| Metrics |
cvssV4_0
|