| 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-2016-5340 | 8/7/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-5244 | 6/27/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-5243 | 6/27/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | High | CVE-2016-5195 | 11/10/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-4998 | 7/3/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-4997 | 7/3/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-4951 | 5/23/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-4913 | 5/23/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-4805 | 5/23/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-4794 | 5/23/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-4581 | 5/23/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-4580 | 5/23/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-4578 | 5/23/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-4569 | 5/23/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-4568 | 5/23/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-4565 | 5/23/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-4558 | 5/23/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-4557 | 5/23/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-4486 | 5/23/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-4485 | 5/23/2016 |