OOBR and OOBW in libpcap before 1.10.7
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| The Tcpdump Group | libpcap | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Tcpdump | Libpcap |
|
Vendor Solution
Upgrade to libpcap 1.10.7.
Vendor Workaround
Validate every filter program that has not been produced by a local call to pcap_compile().
| Source | ID | Title |
|---|---|---|
Ubuntu USN |
USN-8824-1 | libpcap vulnerability |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.108% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Tcpdump
Tcpdump libpcap |
|
| Vendors & Products |
Tcpdump
Tcpdump libpcap |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In BPF instructions that load/store a value from/to a scratch memory register the register index is an unsigned 32-bit integer and must not exceed 15, but libpcap BPF interpreter does not validate the value. In particular uncommon use cases a crafted filter program can cause the interpreter to try reading and writing the OS process memory in the 16GiB starting at the current stack frame on 64-bit architectures and in the entire address space on 32-bit architectures. | |
| Title | OOBR and OOBW in libpcap before 1.10.7 | |
| Weaknesses | CWE-125 CWE-129 CWE-787 |
|
| References |
| |
| Metrics |
cvssV3_1
|