| Version | |
|---|---|
| conf-libelf.1.0.0 (latest) |
| Product | For package | Vendor | Severity | CVE | Published |
|---|---|---|---|---|---|
| elfutils-libelf-devel | conf-libelf.1.0.0 | n/a | Unknown | CVE-2018-18310 | 10/15/2018 |
| libelf-dev | conf-libelf.1.0.0 | n/a | Unknown | CVE-2018-18310 | 10/15/2018 |
| elfutils-dev | conf-libelf.1.0.0 | n/a | Unknown | CVE-2018-18310 | 10/15/2018 |
| libelf | conf-libelf.1.0.0 | n/a | Unknown | CVE-2018-18310 | 10/15/2018 |
| libelf-devel | conf-libelf.1.0.0 | n/a | Unknown | CVE-2018-18310 | 10/15/2018 |
| elfutils-libelf-devel | conf-libelf.1.0.0 | n/a | Unknown | CVE-2018-16403 | 9/3/2018 |
| elfutils-dev | conf-libelf.1.0.0 | n/a | Unknown | CVE-2018-16403 | 9/3/2018 |
| libelf-devel | conf-libelf.1.0.0 | n/a | Unknown | CVE-2018-16403 | 9/3/2018 |
| libelf | conf-libelf.1.0.0 | n/a | Unknown | CVE-2018-16403 | 9/3/2018 |
| libelf-dev | conf-libelf.1.0.0 | n/a | Unknown | CVE-2018-16403 | 9/3/2018 |
| elfutils-dev | conf-libelf.1.0.0 | n/a | Unknown | CVE-2018-16402 | 9/3/2018 |
| libelf | conf-libelf.1.0.0 | n/a | Unknown | CVE-2018-16402 | 9/3/2018 |
| libelf-devel | conf-libelf.1.0.0 | n/a | Unknown | CVE-2018-16402 | 9/3/2018 |
| libelf-dev | conf-libelf.1.0.0 | n/a | Unknown | CVE-2018-16402 | 9/3/2018 |
| elfutils-libelf-devel | conf-libelf.1.0.0 | n/a | Unknown | CVE-2018-16402 | 9/3/2018 |
| libelf-devel | conf-libelf.1.0.0 | n/a | Unknown | CVE-2018-16062 | 8/29/2018 |
| elfutils-dev | conf-libelf.1.0.0 | n/a | Unknown | CVE-2018-16062 | 8/29/2018 |
| elfutils-libelf-devel | conf-libelf.1.0.0 | n/a | Unknown | CVE-2018-16062 | 8/29/2018 |
| libelf-dev | conf-libelf.1.0.0 | n/a | Unknown | CVE-2018-16062 | 8/29/2018 |
| libelf | conf-libelf.1.0.0 | n/a | Unknown | CVE-2018-16062 | 8/29/2018 |