chore(findings): diat/aap-python
Summary
diat/aap-python has 72 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
CVE-2022-2129 | twistlock_cve | Low | vim-common-8.0.1763-19.el8_6.2 |
CVE-2022-2129 | twistlock_cve | Low | vim-enhanced-8.0.1763-19.el8_6.2 |
CVE-2022-2129 | twistlock_cve | Low | vim-filesystem-8.0.1763-19.el8_6.2 |
CVE-2022-2125 | twistlock_cve | Low | vim-common-8.0.1763-19.el8_6.2 |
CVE-2022-2125 | twistlock_cve | Low | vim-enhanced-8.0.1763-19.el8_6.2 |
CVE-2022-2125 | twistlock_cve | Low | vim-filesystem-8.0.1763-19.el8_6.2 |
CVE-2022-2124 | anchore_cve | Low | vim-common-2:8.0.1763-19.el8_6.2 |
CVE-2022-2124 | twistlock_cve | Low | vim-common-8.0.1763-19.el8_6.2 |
CVE-2022-2124 | anchore_cve | Low | vim-enhanced-2:8.0.1763-19.el8_6.2 |
CVE-2022-2124 | twistlock_cve | Low | vim-enhanced-8.0.1763-19.el8_6.2 |
CVE-2022-2124 | anchore_cve | Low | vim-filesystem-2:8.0.1763-19.el8_6.2 |
CVE-2022-2124 | twistlock_cve | Low | vim-filesystem-8.0.1763-19.el8_6.2 |
CVE-2022-2126 | twistlock_cve | Low | vim-common-8.0.1763-19.el8_6.2 |
CVE-2022-2126 | twistlock_cve | Low | vim-enhanced-8.0.1763-19.el8_6.2 |
CVE-2022-2126 | twistlock_cve | Low | vim-filesystem-8.0.1763-19.el8_6.2 |
CVE-2022-2068 | twistlock_cve | Medium | openssl-1.1.1k-6.el8_5 |
CVE-2022-2068 | anchore_cve | Medium | openssl-1:1.1.1k-6.el8_5 |
CVE-2022-1720 | twistlock_cve | Low | vim-common-8.0.1763-19.el8_6.2 |
CVE-2022-1720 | twistlock_cve | Low | vim-enhanced-8.0.1763-19.el8_6.2 |
CVE-2022-1720 | twistlock_cve | Low | vim-filesystem-8.0.1763-19.el8_6.2 |
CVE-2022-2175 | anchore_cve | Low | vim-common-2:8.0.1763-19.el8_6.2 |
CVE-2022-2175 | twistlock_cve | Critical | vim-common-8.0.1763-19.el8_6.2 |
CVE-2022-2175 | anchore_cve | Low | vim-enhanced-2:8.0.1763-19.el8_6.2 |
CVE-2022-2175 | twistlock_cve | Critical | vim-enhanced-8.0.1763-19.el8_6.2 |
CVE-2022-2175 | anchore_cve | Low | vim-filesystem-2:8.0.1763-19.el8_6.2 |
CVE-2022-2175 | twistlock_cve | Critical | vim-filesystem-8.0.1763-19.el8_6.2 |
CVE-2022-2183 | twistlock_cve | Medium | vim-common-8.0.1763-19.el8_6.2 |
CVE-2022-2183 | twistlock_cve | Medium | vim-enhanced-8.0.1763-19.el8_6.2 |
CVE-2022-2183 | twistlock_cve | Medium | vim-filesystem-8.0.1763-19.el8_6.2 |
CVE-2022-2182 | twistlock_cve | Medium | vim-common-8.0.1763-19.el8_6.2 |
CVE-2022-2182 | twistlock_cve | Medium | vim-enhanced-8.0.1763-19.el8_6.2 |
CVE-2022-2182 | twistlock_cve | Medium | vim-filesystem-8.0.1763-19.el8_6.2 |
CVE-2022-2207 | twistlock_cve | Medium | vim-common-8.0.1763-19.el8_6.2 |
CVE-2022-2207 | twistlock_cve | Medium | vim-enhanced-8.0.1763-19.el8_6.2 |
CVE-2022-2207 | twistlock_cve | Medium | vim-filesystem-8.0.1763-19.el8_6.2 |
CVE-2022-2206 | twistlock_cve | Medium | vim-common-8.0.1763-19.el8_6.2 |
CVE-2022-2206 | twistlock_cve | Medium | vim-enhanced-8.0.1763-19.el8_6.2 |
CVE-2022-2206 | twistlock_cve | Medium | vim-filesystem-8.0.1763-19.el8_6.2 |
CVE-2022-2231 | twistlock_cve | Medium | vim-common-8.0.1763-19.el8_6.2 |
CVE-2022-2231 | twistlock_cve | Medium | vim-enhanced-8.0.1763-19.el8_6.2 |
CVE-2022-2231 | twistlock_cve | Medium | vim-filesystem-8.0.1763-19.el8_6.2 |
CVE-2022-2210 | twistlock_cve | Medium | vim-common-8.0.1763-19.el8_6.2 |
CVE-2022-2210 | twistlock_cve | Medium | vim-enhanced-8.0.1763-19.el8_6.2 |
CVE-2022-2210 | twistlock_cve | Medium | vim-filesystem-8.0.1763-19.el8_6.2 |
CVE-2022-2208 | twistlock_cve | Low | vim-common-8.0.1763-19.el8_6.2 |
CVE-2022-2208 | twistlock_cve | Low | vim-enhanced-8.0.1763-19.el8_6.2 |
CVE-2022-2208 | twistlock_cve | Low | vim-filesystem-8.0.1763-19.el8_6.2 |
CVE-2022-33070 | anchore_cve | Low | protobuf-c-1.3.0-6.el8 |
CVE-2022-33070 | twistlock_cve | Low | protobuf-c-1.3.0-6.el8 |
CVE-2022-2257 | twistlock_cve | Low | vim-common-8.0.1763-19.el8_6.2 |
CVE-2022-2257 | twistlock_cve | Low | vim-enhanced-8.0.1763-19.el8_6.2 |
CVE-2022-2257 | twistlock_cve | Low | vim-filesystem-8.0.1763-19.el8_6.2 |
CVE-2022-2288 | twistlock_cve | Low | vim-common-8.0.1763-19.el8_6.2 |
CVE-2022-2288 | twistlock_cve | Low | vim-enhanced-8.0.1763-19.el8_6.2 |
CVE-2022-2288 | twistlock_cve | Low | vim-filesystem-8.0.1763-19.el8_6.2 |
CVE-2022-2289 | twistlock_cve | Low | vim-common-8.0.1763-19.el8_6.2 |
CVE-2022-2289 | twistlock_cve | Low | vim-enhanced-8.0.1763-19.el8_6.2 |
CVE-2022-2289 | twistlock_cve | Low | vim-filesystem-8.0.1763-19.el8_6.2 |
CVE-2022-2286 | twistlock_cve | Low | vim-common-8.0.1763-19.el8_6.2 |
CVE-2022-2286 | twistlock_cve | Low | vim-enhanced-8.0.1763-19.el8_6.2 |
CVE-2022-2286 | twistlock_cve | Low | vim-filesystem-8.0.1763-19.el8_6.2 |
CVE-2022-2285 | twistlock_cve | Low | vim-common-8.0.1763-19.el8_6.2 |
CVE-2022-2285 | twistlock_cve | Low | vim-enhanced-8.0.1763-19.el8_6.2 |
CVE-2022-2285 | twistlock_cve | Low | vim-filesystem-8.0.1763-19.el8_6.2 |
CVE-2022-2284 | twistlock_cve | Low | vim-common-8.0.1763-19.el8_6.2 |
CVE-2022-2284 | twistlock_cve | Low | vim-enhanced-8.0.1763-19.el8_6.2 |
CVE-2022-2284 | twistlock_cve | Low | vim-filesystem-8.0.1763-19.el8_6.2 |
CVE-2022-2287 | twistlock_cve | Low | vim-common-8.0.1763-19.el8_6.2 |
CVE-2022-2287 | twistlock_cve | Low | vim-enhanced-8.0.1763-19.el8_6.2 |
CVE-2022-2287 | twistlock_cve | Low | vim-filesystem-8.0.1763-19.el8_6.2 |
CVE-2022-2097 | twistlock_cve | Medium | openssl-1.1.1k-6.el8_5 |
CVE-2022-2097 | anchore_cve | Medium | openssl-1:1.1.1k-6.el8_5 |
VAT: https://vat.dso.mil/vat/container/19830?branch=master
More information can be found in the failed pipeline located here: https://repo1.dso.mil/dsop/diat/aap-python/-/jobs/12785133
Tasks
Contributor:
-
Provide justifications for findings in the VAT (docs) -
Apply the ~"Approval" label to this issue and wait for feedback
Iron Bank:
-
Review findings and justifications -
Send approval request to Authorizing Official -
Close issue after approval from Authorizing Official
Note: If the above approval process is rejected for any reason, the
Approval
label will be removed and the issue will be sent back toOpen
. Any comments will be listed in this issue for you to address. Once they have been addressed, you must re-add theApproval
label.
Questions?
Contact the Iron Bank team by commenting on this issue with your questions or concerns. If you do not receive a response, add /cc @ironbank-notifications/onboarding
.
Additionally, Iron Bank hosts an AMA working session every Wednesday from 1630-1730EST to answer questions.