chore(findings): atlassian/confluence-data-center/confluence-node
Summary
atlassian/confluence-data-center/confluence-node has 107 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
CVE-2019-11358 | Anchore CVE | Medium | jquery-2.2.4.7 |
CVE-2016-6325 | Anchore CVE | High | tomcat-dbcp-9.0.86 |
CVE-2020-11022 | Anchore CVE | Medium | jquery-2.2.4.7 |
CVE-2016-5425 | Anchore CVE | High | tomcat-util-scan-9.0.86 |
CVE-2016-6325 | Anchore CVE | High | tomcat-jni-9.0.86 |
CVE-2016-5425 | Anchore CVE | High | tomcat-juli-9.0.86 |
GHSA-2mrq-w8pv-5pvq | Anchore CVE | Medium | antisamy-1.6.8-atlassian-5 |
CVE-2016-5425 | Anchore CVE | High | tomcat-i18n-ja-9.0.86 |
CVE-2019-17571 | Anchore CVE | Critical | 2-api-1.2-api-2.19.0 |
CVE-2015-9251 | Anchore CVE | Medium | jquery-2.2.4.12 |
CVE-2020-11022 | Anchore CVE | Medium | jquery-2.2.4.12 |
GHSA-2wrp-6fg6-hmc5 | Anchore CVE | High | spring-web-5.3.32 |
CVE-2016-6325 | Anchore CVE | High | tomcat-api-9.0.86 |
CVE-2019-11358 | Anchore CVE | Medium | jquery-2.2.4.12 |
CVE-2022-45064 | Anchore CVE | Critical | org.apache.sling.scripting.jsp-2.6.2-atlassian-1 |
CVE-2007-2379 | Anchore CVE | Medium | jquery-2.2.4.12 |
CVE-2022-45064 | Anchore CVE | Critical | org.apache.sling.commons.osgi-2.0.4-incubator |
CVE-2023-35116 | Anchore CVE | Medium | jackson-databind-2.15.2 |
GHSA-hgjh-9rj2-g67j | Anchore CVE | High | spring-web-5.3.32 |
CVE-2016-6325 | Anchore CVE | High | tomcat-i18n-ko-9.0.86 |
CVE-2016-6325 | Anchore CVE | High | tomcat-i18n-pt-BR-9.0.86 |
CVE-2020-11023 | Anchore CVE | Medium | jquery-2.2.4.12 |
GHSA-pcf2-gh6g-h5r2 | Anchore CVE | Medium | antisamy-1.6.8-atlassian-7 |
CVE-2023-37895 | Anchore CVE | Critical | jackrabbit-webdav-2.21.16 |
CVE-2016-6325 | Anchore CVE | High | tomcat-i18n-cs-9.0.86 |
GHSA-gvpg-vgmx-xg6w | Anchore CVE | Medium | nimbus-jose-jwt-9.31 |
CVE-2016-5425 | Anchore CVE | High | tomcat-i18n-es-9.0.86 |
CVE-2023-43804 | Anchore CVE | Medium | platform-python-pip-9.0.3-23.el8_9.1 |
GHSA-gvpg-vgmx-xg6w | Anchore CVE | Medium | nimbus-jose-jwt-9.31 |
CVE-2023-37895 | Anchore CVE | Critical | jackrabbit-jcr-commons-2.21.16 |
GHSA-pcf2-gh6g-h5r2 | Anchore CVE | Medium | antisamy-1.6.8-atlassian-5 |
GHSA-gvpg-vgmx-xg6w | Anchore CVE | Medium | nimbus-jose-jwt-8.22 |
GHSA-2mrq-w8pv-5pvq | Anchore CVE | Medium | antisamy-1.6.8-atlassian-7 |
CVE-2016-5425 | Anchore CVE | High | tomcat-i18n-ko-9.0.86 |
CVE-2016-5425 | Anchore CVE | High | tomcat-coyote-9.0.86 |
CVE-2016-5425 | Anchore CVE | High | tomcat-websocket-9.0.86 |
CVE-2018-20406 | Anchore CVE | Low | python36-3.6.8-38.module+el8.9.0+20976+d3c38525 |
CVE-2016-6325 | Anchore CVE | High | tomcat-i18n-zh-CN-9.0.86 |
CVE-2007-2379 | Anchore CVE | Medium | jquery-2.2.4.7 |
CVE-2013-4390 | Anchore CVE | Medium | org.apache.sling.commons.osgi-2.0.4-incubator |
CVE-2018-20225 | Anchore CVE | Low | platform-python-pip-9.0.3-23.el8_9.1 |
CVE-2020-23064 | Anchore CVE | Medium | jquery-2.2.4.12 |
CVE-2020-13959 | Anchore CVE | Medium | velocity-tools-2.0.1-atlassian-2 |
GHSA-4g9r-vxhx-9pgx | Anchore CVE | High | commons-compress-1.24.0 |
CVE-2020-23064 | Anchore CVE | Medium | jquery-2.2.4.7 |
CVE-2016-5425 | Anchore CVE | High | tomcat-i18n-fr-9.0.86 |
CVE-2016-5425 | Anchore CVE | High | tomcat-i18n-ru-9.0.86 |
CVE-2023-43804 | Anchore CVE | Medium | python3-pip-9.0.3-23.el8_9.1 |
CVE-2022-23307 | Anchore CVE | High | 2-api-1.2-api-2.19.0 |
CVE-2022-23302 | Anchore CVE | High | 2-api-1.2-api-2.19.0 |
CVE-2020-23064 | Anchore CVE | Medium | jquery-2.2.4.12 |
GHSA-4265-ccf5-phj5 | Anchore CVE | High | commons-compress-1.24.0 |
CVE-2020-9493 | Anchore CVE | Critical | 2-api-1.2-api-2.19.0 |
CVE-2022-23305 | Anchore CVE | Critical | 2-api-1.2-api-2.19.0 |
GHSA-59j4-wjwp-mw9m | Anchore CVE | High | velocity-1.6.4-atlassian-28 |
CVE-2023-35116 | Anchore CVE | Medium | jackson-databind-2.15.3 |
GHSA-gvpg-vgmx-xg6w | Anchore CVE | Medium | nimbus-jose-jwt-8.20.1 |
CVE-2020-11023 | Anchore CVE | Medium | jquery-2.2.4.12 |
GHSA-vr64-r9qj-h27f | Anchore CVE | Medium | clojure-1.11.1 |
CVE-2016-6325 | Anchore CVE | High | tomcat-websocket-9.0.86 |
CVE-2013-4390 | Anchore CVE | Medium | org.apache.sling.scripting.jsp-2.6.2-atlassian-1 |
CVE-2016-5425 | Anchore CVE | High | tomcat-i18n-de-9.0.86 |
CVE-2018-20225 | Anchore CVE | Low | python3-pip-9.0.3-23.el8_9.1 |
CVE-2022-36437 | Anchore CVE | Critical | hazelcast-micrometer-2.0.0 |
CVE-2016-0956 | Anchore CVE | High | org.apache.sling.commons.osgi-2.0.4-incubator |
CVE-2016-5425 | Anchore CVE | High | tomcat-api-9.0.86 |
CVE-2020-11023 | Anchore CVE | Medium | jquery-2.2.4.7 |
CVE-2019-9674 | Anchore CVE | Low | python36-3.6.8-38.module+el8.9.0+20976+d3c38525 |
CVE-2016-5425 | Anchore CVE | High | tomcat-i18n-zh-CN-9.0.86 |
CVE-2023-35116 | Anchore CVE | Medium | jackson-databind-2.13.4.2 |
GHSA-5jpm-x58v-624v | Anchore CVE | Medium | netty-codec-http-4.1.100.Final |
CVE-2016-5425 | Anchore CVE | High | tomcat-i18n-pt-BR-9.0.86 |
CVE-2016-10750 | Anchore CVE | High | hazelcast-micrometer-2.0.0 |
CVE-2023-35116 | Anchore CVE | Medium | jackson-databind-2.15.2 |
GHSA-5jpm-x58v-624v | Anchore CVE | Medium | netty-codec-http-4.1.100.Final |
CVE-2016-6325 | Anchore CVE | High | tomcat-i18n-fr-9.0.86 |
CVE-2023-26464 | Anchore CVE | High | 2-api-1.2-api-2.19.0 |
GHSA-2mrq-w8pv-5pvq | Anchore CVE | Medium | antisamy-1.6.8-atlassian-5 |
CVE-2016-6325 | Anchore CVE | High | tomcat-i18n-de-9.0.86 |
CVE-2016-6325 | Anchore CVE | High | tomcat-i18n-ru-9.0.86 |
GHSA-5jpm-x58v-624v | Anchore CVE | Medium | netty-codec-http-4.1.100.Final |
CVE-2016-5425 | Anchore CVE | High | tomcat-util-9.0.86 |
CVE-2023-35116 | Anchore CVE | Medium | jackson-databind-2.12.7.1 |
CVE-2016-6325 | Anchore CVE | High | tomcat-i18n-es-9.0.86 |
GHSA-gvpg-vgmx-xg6w | Anchore CVE | Medium | nimbus-jose-jwt-9.31 |
CVE-2016-6325 | Anchore CVE | High | tomcat-util-9.0.86 |
CVE-2016-0956 | Anchore CVE | High | org.apache.sling.scripting.jsp-2.6.2-atlassian-1 |
GHSA-2363-cqg2-863c | Anchore CVE | High | jdom-1.1.3-atlassian-5 |
CVE-2016-5425 | Anchore CVE | High | tomcat-jni-9.0.86 |
CVE-2023-37895 | Anchore CVE | Critical | jackrabbit-spi-2.21.16 |
CVE-2023-33264 | Anchore CVE | Medium | hazelcast-micrometer-2.0.0 |
GHSA-3832-9276-x7gf | Anchore CVE | Medium | commons-httpclient-3.1-atlassian-2 |
CVE-2015-9251 | Anchore CVE | Medium | jquery-2.2.4.12 |
CVE-2023-37895 | Anchore CVE | Critical | jackrabbit-spi-commons-2.21.16 |
CVE-2016-6325 | Anchore CVE | High | tomcat-juli-9.0.86 |
CVE-2023-37895 | Anchore CVE | Critical | jackrabbit-jcr-server-2.21.16 |
CVE-2016-6325 | Anchore CVE | High | tomcat-coyote-9.0.86 |
GHSA-pcf2-gh6g-h5r2 | Anchore CVE | Medium | antisamy-1.6.8-atlassian-5 |
CVE-2016-6325 | Anchore CVE | High | tomcat-i18n-ja-9.0.86 |
CVE-2016-5425 | Anchore CVE | High | tomcat-i18n-cs-9.0.86 |
CVE-2007-2379 | Anchore CVE | Medium | jquery-2.2.4.12 |
CVE-2020-11022 | Anchore CVE | Medium | jquery-2.2.4.12 |
CVE-2016-5425 | Anchore CVE | High | tomcat-dbcp-9.0.86 |
CVE-2016-6325 | Anchore CVE | High | tomcat-util-scan-9.0.86 |
CVE-2015-9251 | Anchore CVE | Medium | jquery-2.2.4.7 |
CVE-2019-11358 | Anchore CVE | Medium | jquery-2.2.4.12 |
CVE-2024-34064 | Twistlock CVE | Medium | jinja2-2.10.1 |
VAT: https://vat.dso.mil/vat/image?imageName=atlassian/confluence-data-center/confluence-node&tag=8.9.0&branch=master
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=atlassian/confluence-data-center/confluence-node&tag=8.9.0&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.