| Version | |
|---|---|
| bap-llvm.2.5.0 (latest) | |
| bap-llvm.2.4.0 | |
| bap-llvm.2.3.0 | |
| bap-llvm.2.2.0 | |
| bap-llvm.2.1.0 |
| Product | For package | Vendor | Severity | CVE | Published |
|---|---|---|---|---|---|
| libncurses5-dev | bap-llvm.2.2.0 | n/a | Unknown | CVE-2017-13732 | 8/29/2017 |
| libncurses5-dev | bap-llvm.2.1.0 | n/a | Unknown | CVE-2017-13732 | 8/29/2017 |
| libncurses5-dev | bap-llvm.2.5.0 | n/a | Unknown | CVE-2017-13732 | 8/29/2017 |
| libncurses5-dev | bap-llvm.2.3.0 | n/a | Unknown | CVE-2017-13732 | 8/29/2017 |
| libncurses5-dev | bap-llvm.2.4.0 | n/a | Unknown | CVE-2017-13732 | 8/29/2017 |
| libncurses5-dev | bap-llvm.2.5.0 | n/a | Unknown | CVE-2017-13731 | 8/29/2017 |
| libncurses5-dev | bap-llvm.2.1.0 | n/a | Unknown | CVE-2017-13731 | 8/29/2017 |
| libncurses5-dev | bap-llvm.2.2.0 | n/a | Unknown | CVE-2017-13731 | 8/29/2017 |
| libncurses5-dev | bap-llvm.2.4.0 | n/a | Unknown | CVE-2017-13731 | 8/29/2017 |
| libncurses5-dev | bap-llvm.2.3.0 | n/a | Unknown | CVE-2017-13731 | 8/29/2017 |
| libncurses5-dev | bap-llvm.2.5.0 | n/a | Unknown | CVE-2017-13730 | 8/29/2017 |
| libncurses5-dev | bap-llvm.2.1.0 | n/a | Unknown | CVE-2017-13730 | 8/29/2017 |
| libncurses5-dev | bap-llvm.2.3.0 | n/a | Unknown | CVE-2017-13730 | 8/29/2017 |
| libncurses5-dev | bap-llvm.2.2.0 | n/a | Unknown | CVE-2017-13730 | 8/29/2017 |
| libncurses5-dev | bap-llvm.2.4.0 | n/a | Unknown | CVE-2017-13730 | 8/29/2017 |
| libncurses5-dev | bap-llvm.2.1.0 | n/a | Unknown | CVE-2017-13729 | 8/29/2017 |
| libncurses5-dev | bap-llvm.2.3.0 | n/a | Unknown | CVE-2017-13729 | 8/29/2017 |
| libncurses5-dev | bap-llvm.2.5.0 | n/a | Unknown | CVE-2017-13729 | 8/29/2017 |
| libncurses5-dev | bap-llvm.2.2.0 | n/a | Unknown | CVE-2017-13729 | 8/29/2017 |
| libncurses5-dev | bap-llvm.2.4.0 | n/a | Unknown | CVE-2017-13729 | 8/29/2017 |