| Version | |
|---|---|
| conf-libbpf.0.1.0 (latest) |
| Product | For package | Vendor | Severity | CVE | Published |
|---|---|---|---|---|---|
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2017-1000379 | 6/19/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2017-1000371 | 6/19/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2017-1000370 | 6/19/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2017-1000365 | 6/19/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2017-1000364 | 6/19/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2017-1000363 | 7/13/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | High | CVE-2017-1000253 | 10/4/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2017-1000252 | 9/26/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2017-1000251 | 9/12/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2017-1000112 | 10/4/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2017-1000111 | 10/4/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | Google Inc. | Unknown | CVE-2017-0651 | 6/14/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | Google Inc. | Unknown | CVE-2017-0650 | 6/14/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | Google Inc. | Unknown | CVE-2017-0648 | 6/14/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2017-0634 | 5/12/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | Google Inc. | Unknown | CVE-2017-0633 | 5/12/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | Google Inc. | Unknown | CVE-2017-0632 | 5/12/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | Google Inc. | Unknown | CVE-2017-0631 | 5/12/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | Google Inc. | Unknown | CVE-2017-0630 | 5/12/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | Google Inc. | Unknown | CVE-2017-0629 | 5/12/2017 |