chore(findings): opensource/apache/guacamole/guacamole-client
Summary
opensource/apache/guacamole/guacamole-client has 65 new findings discovered during continuous monitoring.
| id | source | package |
|---|---|---|
| CVE-2021-22898 | anchore_cve | guacamole-1.3.0 |
| CVE-2021-22898 | anchore_cve | guacamole-1.3.0 |
| CVE-2021-22898 | anchore_cve | guacamole-1.3.0 |
| CVE-2021-22898 | anchore_cve | guacamole-1.3.0 |
| CVE-2021-22898 | anchore_cve | guacamole-1.3.0 |
| CVE-2021-22898 | anchore_cve | guacamole-1.3.0 |
| CVE-2021-22898 | anchore_cve | guacamole-1.3.0 |
| CVE-2021-22898 | anchore_cve | guacamole-1.3.0 |
| CVE-2021-22898 | anchore_cve | guacamole-1.3.0 |
| CVE-2021-22898 | anchore_cve | guacamole-1.3.0 |
| CVE-2021-22898 | anchore_cve | guacamole-1.3.0 |
| CVE-2021-22898 | anchore_cve | guacamole-1.3.0 |
| CVE-2021-22898 | anchore_cve | guacamole-1.3.0 |
| CVE-2021-3516 | anchore_cve | libxml2-2.9.7-9.el8 |
| CVE-2021-3517 | anchore_cve | libxml2-2.9.7-9.el8 |
| CVE-2021-3518 | anchore_cve | libxml2-2.9.7-9.el8 |
| CVE-2021-3537 | anchore_cve | libxml2-2.9.7-9.el8 |
| CVE-2021-3541 | anchore_cve | libxml2-2.9.7-9.el8 |
| CVE-2021-3520 | anchore_cve | lz4-libs-1.8.3-2.el8 |
| CVE-2021-3516 | anchore_cve | python3-libxml2-2.9.7-9.el8 |
| CVE-2021-3517 | anchore_cve | python3-libxml2-2.9.7-9.el8 |
| CVE-2021-3518 | anchore_cve | python3-libxml2-2.9.7-9.el8 |
| CVE-2021-3537 | anchore_cve | python3-libxml2-2.9.7-9.el8 |
| CVE-2021-3541 | anchore_cve | python3-libxml2-2.9.7-9.el8 |
| CVE-2021-20266 | anchore_cve | python3-rpm-4.14.3-13.el8 |
| CVE-2021-20271 | anchore_cve | python3-rpm-4.14.3-13.el8 |
| CVE-2021-3421 | anchore_cve | python3-rpm-4.14.3-13.el8 |
| CVE-2021-35937 | anchore_cve | python3-rpm-4.14.3-13.el8 |
| CVE-2021-35938 | anchore_cve | python3-rpm-4.14.3-13.el8 |
| CVE-2021-35939 | anchore_cve | python3-rpm-4.14.3-13.el8 |
| CVE-2021-20266 | anchore_cve | rpm-4.14.3-13.el8 |
| CVE-2021-20271 | anchore_cve | rpm-4.14.3-13.el8 |
| CVE-2021-3421 | anchore_cve | rpm-4.14.3-13.el8 |
| CVE-2021-35937 | anchore_cve | rpm-4.14.3-13.el8 |
| CVE-2021-35938 | anchore_cve | rpm-4.14.3-13.el8 |
| CVE-2021-35939 | anchore_cve | rpm-4.14.3-13.el8 |
| CVE-2021-20266 | anchore_cve | rpm-build-libs-4.14.3-13.el8 |
| CVE-2021-20271 | anchore_cve | rpm-build-libs-4.14.3-13.el8 |
| CVE-2021-3421 | anchore_cve | rpm-build-libs-4.14.3-13.el8 |
| CVE-2021-35937 | anchore_cve | rpm-build-libs-4.14.3-13.el8 |
| CVE-2021-35938 | anchore_cve | rpm-build-libs-4.14.3-13.el8 |
| CVE-2021-35939 | anchore_cve | rpm-build-libs-4.14.3-13.el8 |
| CVE-2021-20266 | anchore_cve | rpm-libs-4.14.3-13.el8 |
| CVE-2021-20271 | anchore_cve | rpm-libs-4.14.3-13.el8 |
| CVE-2021-3421 | anchore_cve | rpm-libs-4.14.3-13.el8 |
| CVE-2021-35937 | anchore_cve | rpm-libs-4.14.3-13.el8 |
| CVE-2021-35938 | anchore_cve | rpm-libs-4.14.3-13.el8 |
| CVE-2021-35939 | anchore_cve | rpm-libs-4.14.3-13.el8 |
| CVE-2021-3516 | twistlock_cve | libxml2-2.9.7-9.el8 |
| CVE-2021-3517 | twistlock_cve | libxml2-2.9.7-9.el8 |
| CVE-2021-3518 | twistlock_cve | libxml2-2.9.7-9.el8 |
| CVE-2021-3537 | twistlock_cve | libxml2-2.9.7-9.el8 |
| CVE-2021-3541 | twistlock_cve | libxml2-2.9.7-9.el8 |
| CVE-2021-3520 | twistlock_cve | lz4-libs-1.8.3-2.el8 |
| CVE-2021-3516 | twistlock_cve | python3-libxml2-2.9.7-9.el8 |
| CVE-2021-3517 | twistlock_cve | python3-libxml2-2.9.7-9.el8 |
| CVE-2021-3518 | twistlock_cve | python3-libxml2-2.9.7-9.el8 |
| CVE-2021-3537 | twistlock_cve | python3-libxml2-2.9.7-9.el8 |
| CVE-2021-3541 | twistlock_cve | python3-libxml2-2.9.7-9.el8 |
| CVE-2021-20271 | twistlock_cve | python3-rpm-4.14.3-13.el8 |
| CVE-2021-20266 | twistlock_cve | rpm-4.14.3-13.el8 |
| CVE-2021-20271 | twistlock_cve | rpm-4.14.3-13.el8 |
| CVE-2021-3421 | twistlock_cve | rpm-4.14.3-13.el8 |
| CVE-2021-20271 | twistlock_cve | rpm-build-libs-4.14.3-13.el8 |
| CVE-2021-20271 | twistlock_cve | rpm-libs-4.14.3-13.el8 |
More information can be found in the failed pipeline located here: https://repo1.dso.mil/dsop/opensource/apache/guacamole/guacamole-client/-/jobs/4608755
Definition of Done
Justifications:
-
All findings have been justified -
Justifications have been provided to the container hardening team
Approval Process:
-
Findings Approver has reviewed and approved all justifications -
Approval request has been sent to Authorizing Official -
Approval request has been processed by Authorizing Official