OOBR 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 and migrate from bpf_filter() to pcap_offline_filter().
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.105% 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 | libpcap BPF interpreter detects neither reaching the end of the filter program buffer due to lack of a return instruction nor executing a jump instruction with an offset that translates to a pointer outside of the buffer. In particular uncommon use cases a crafted filter program can cause the interpreter to try reading the OS process memory in the 32GiB around the buffer on 64-bit architectures and in the entire address space on 32-bit architectures. | |
| Title | OOBR in libpcap before 1.10.7 | |
| Weaknesses | CWE-125 CWE-1285 CWE-823 |
|
| References |
| |
| Metrics |
cvssV3_1
|