librtmp (RTMPDump) through 2.6 Heap Out-of-Bounds Read via AMFProp_Decode
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| RTMPDump | librtmp | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Rtmpdump | Librtmp |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.221% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Rtmpdump
Rtmpdump librtmp |
|
| Vendors & Products |
Rtmpdump
Rtmpdump librtmp |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | librtmp (RTMPDump) through 2.6 contains a heap out-of-bounds read vulnerability in AMFProp_Decode that reads an AMF0 strict-array element count before checking that four bytes remain. A malicious RTMP server or man in the middle can send an AMF0 body ending with a strict-array type byte and fewer than four trailing bytes to crash the client. | |
| Title | librtmp (RTMPDump) through 2.6 Heap Out-of-Bounds Read via AMFProp_Decode | |
| Weaknesses | CWE-125 | |
| References |
|
|
| Metrics |
cvssV3_1
|