chore(findings): opensource/python
Summary
opensource/python has 88 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
CVE-2021-4166 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-3705 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-2125 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-2183 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2023-0054 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-2849 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-3234 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-2980 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-4141 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-4293 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2023-4781 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-2182 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-3297 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2023-4734 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2023-4735 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2021-3928 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-2889 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-2129 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2023-4738 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2023-1127 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-3134 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-2819 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-3256 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-2946 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-2286 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2023-1264 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-3352 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2023-2609 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-2257 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-2344 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-2287 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-4292 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-2124 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-2817 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-3037 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2023-0433 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-1720 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-1616 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2023-0049 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-2522 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-3099 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-1619 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-3324 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-3153 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2023-0051 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-2874 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2021-3927 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-0213 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2023-5344 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-2345 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-1620 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2021-4187 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-3296 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2023-5441 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2023-5535 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-2304 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2021-3973 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-2862 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2023-0288 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2021-3974 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2023-2610 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2023-1170 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2020-20703 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2023-1175 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-2284 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2021-4136 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2023-0512 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-2126 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2023-4751 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2023-46246 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-2845 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-2285 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-3235 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2021-4173 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-2042 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-2982 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2021-3968 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-0351 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-2923 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-2206 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-2343 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-2175 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-2210 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-2208 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-1725 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-3278 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-2207 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
CVE-2022-3016 | Anchore CVE | Low | vim-filesystem-2:8.2.2637-20.el9_1 |
VAT: https://vat.dso.mil/vat/image?imageName=opensource/python&tag=v3.9&branch=master
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensource/python&tag=v3.9&branch=master
Tasks
Contributor:
-
Provide justifications for findings in the VAT (docs) -
Apply the StatusVerification label to this issue and wait for feedback
Iron Bank:
-
Review findings and justifications
Note: If the above process is rejected for any reason, the
Verification
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 theVerification
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.