| 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-5548 | 2/6/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2017-5547 | 2/6/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2017-5546 | 2/6/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2017-5123 | 11/2/2021 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2017-2671 | 4/5/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2017-2647 | 3/31/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2017-2636 | 3/7/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | Linux | High | CVE-2017-2634 | 7/27/2018 |
| libbpf-dev | conf-libbpf.0.1.0 | Linux | Medium | CVE-2017-2618 | 7/27/2018 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2017-2596 | 2/6/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2017-2584 | 1/15/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2017-2583 | 2/6/2017 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2017-18595 | 9/4/2019 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2017-18552 | 8/19/2019 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2017-18551 | 8/19/2019 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2017-18550 | 8/19/2019 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2017-18549 | 8/19/2019 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2017-18509 | 8/13/2019 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2017-18379 | 7/27/2019 |
| libbpf-dev | conf-libbpf.0.1.0 | n/a | Unknown | CVE-2017-18360 | 1/31/2019 |