| 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-2018-14616 | 7/27/2018 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2018-14615 | 7/27/2018 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2018-14614 | 7/27/2018 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2018-14613 | 7/27/2018 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2018-14612 | 7/27/2018 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2018-14611 | 7/27/2018 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2018-14610 | 7/27/2018 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2018-14609 | 7/27/2018 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2018-13406 | 7/6/2018 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2018-13405 | 7/6/2018 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2018-13100 | 7/3/2018 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2018-13099 | 7/3/2018 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2018-13098 | 7/3/2018 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2018-13097 | 7/3/2018 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2018-13096 | 7/3/2018 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2018-13095 | 7/3/2018 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2018-13094 | 7/3/2018 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2018-13093 | 7/3/2018 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2018-13053 | 7/2/2018 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2018-12931 | 6/28/2018 |