| Version | |
|---|---|
| conf-libbpf.0.1.0 (latest) |
| Product | For package | Vendor | Severity | CVE | Published |
|---|---|---|---|---|---|
| libbpf-dev | conf-libbpf.0.1.0 | Google Inc. | Unknown | CVE-2016-10284 | 5/12/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | Google Inc. | Unknown | CVE-2016-10283 | 5/12/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | Google Inc. | Unknown | CVE-2016-10277 | 5/12/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-10229 | 4/4/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-10208 | 2/6/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-10200 | 3/7/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-10154 | 2/6/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-10153 | 2/6/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-10150 | 2/6/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-10147 | 1/18/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-10088 | 12/30/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-10044 | 2/7/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-0823 | 3/12/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-0821 | 3/12/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-0758 | 6/27/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-0728 | 2/8/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2016-0723 | 2/8/2016 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2015-9289 | 7/27/2019 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2015-9004 | 5/2/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2015-8970 | 11/28/2016 |