chore(findings): microfocus/fortify/ssc
Summary
microfocus/fortify/ssc has 107 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
GHSA-v682-8vv8-vpwr | Anchore CVE | Medium | tomcat-websocket-9.0.84 |
CVE-2016-5425 | Anchore CVE | High | tomcat-i18n-ru-9.0.84 |
CVE-2022-42890 | Anchore CVE | High | org.apache.batik.script-1.14.0-SNAPSHOT |
CVE-2016-5425 | Anchore CVE | High | tomcat-api-9.0.84 |
GHSA-2wrp-6fg6-hmc5 | Anchore CVE | High | spring-web-5.3.29 |
CVE-2022-42890 | Anchore CVE | High | org.apache.batik.parser-1.14.0-SNAPSHOT |
GHSA-hgjh-9rj2-g67j | Anchore CVE | High | spring-web-5.3.29 |
CVE-2016-6325 | Anchore CVE | High | tomcat-i18n-ru-9.0.84 |
CVE-2022-41704 | Anchore CVE | High | org.apache.batik.anim-1.14.0-SNAPSHOT |
CVE-2020-27225 | Anchore CVE | High | org.eclipse.core.contenttype-3.9.0 |
CVE-2022-42890 | Anchore CVE | High | org.apache.batik.codec-1.14.0-SNAPSHOT |
CVE-2022-42890 | Anchore CVE | High | org.apache.batik.bridge-1.14.0-SNAPSHOT |
CVE-2015-4035 | Anchore CVE | High | xz-1.9.0 |
CVE-2022-42890 | Anchore CVE | High | org.apache.batik.constants-1.14.0-SNAPSHOT |
CVE-2020-27225 | Anchore CVE | High | org.eclipse.core.jobs-3.14.0 |
CVE-2022-41704 | Anchore CVE | High | org.apache.batik.script-1.14.0-SNAPSHOT |
CVE-2020-27225 | Anchore CVE | High | org.eclipse.equinox.registry-3.11.200 |
CVE-2016-6325 | Anchore CVE | High | tomcat-i18n-es-9.0.84 |
CVE-2022-41704 | Anchore CVE | High | org.apache.batik.css-1.14.0-SNAPSHOT |
CVE-2022-42890 | Anchore CVE | High | org.apache.batik.transcoder-1.14.0-SNAPSHOT |
CVE-2020-27225 | Anchore CVE | High | org.eclipse.text-3.13.0 |
CVE-2020-27225 | Anchore CVE | High | org.eclipse.core.filesystem-1.10.0 |
CVE-2022-41704 | Anchore CVE | High | org.apache.batik.dom-1.14.0-SNAPSHOT |
CVE-2022-26336 | Anchore CVE | Medium | org.apache.poi.ooxml.schemas-4.1.1-SNAPSHOT |
CVE-2016-5425 | Anchore CVE | High | tomcat-i18n-ja-9.0.84 |
CVE-2016-6325 | Anchore CVE | High | tomcat-api-9.0.84 |
CVE-2016-5425 | Anchore CVE | High | tomcat-i18n-de-9.0.84 |
CVE-2022-42890 | Anchore CVE | High | org.apache.batik.anim-1.14.0-SNAPSHOT |
CVE-2016-5425 | Anchore CVE | High | tomcat-i18n-fr-9.0.84 |
CVE-2022-42890 | Anchore CVE | High | org.apache.batik.i18n-1.14.0-SNAPSHOT |
CVE-2022-42890 | Anchore CVE | High | org.apache.batik.dom-1.14.0-SNAPSHOT |
CVE-2016-5425 | Anchore CVE | High | tomcat-i18n-es-9.0.84 |
CVE-2022-41704 | Anchore CVE | High | org.apache.batik.util-1.14.0-SNAPSHOT |
CVE-2016-5425 | Anchore CVE | High | tomcat-jni-9.0.84 |
GHSA-j24h-xcpc-9jw8 | Anchore CVE | Medium | org.eclipse.core.runtime-3.27.0 |
CVE-2022-42890 | Anchore CVE | High | org.apache.batik.svggen-1.14.0-SNAPSHOT |
CVE-2022-42890 | Anchore CVE | High | org.apache.batik.gvt-1.14.0-SNAPSHOT |
CVE-2022-42890 | Anchore CVE | High | org.apache.batik.xml-1.14.0-SNAPSHOT |
CVE-2020-27225 | Anchore CVE | High | org.eclipse.equinox.app-1.6.200 |
CVE-2022-41704 | Anchore CVE | High | org.apache.batik.i18n-1.14.0-SNAPSHOT |
CVE-2016-5425 | Anchore CVE | High | tomcat-util-9.0.84 |
CVE-2022-41704 | Anchore CVE | High | org.apache.batik.xml-1.14.0-SNAPSHOT |
GHSA-jjfh-589g-3hjx | Anchore CVE | Medium | spring-boot-2.7.14 |
CVE-2016-6325 | Anchore CVE | High | tomcat-juli-9.0.84 |
CVE-2016-6325 | Anchore CVE | High | tomcat-util-scan-9.0.84 |
CVE-2022-41704 | Anchore CVE | High | org.apache.batik.codec-1.14.0-SNAPSHOT |
CVE-2022-41704 | Anchore CVE | High | org.apache.batik.bridge-1.14.0-SNAPSHOT |
CVE-2020-27225 | Anchore CVE | High | org.eclipse.osgi-3.18.400 |
CVE-2016-6325 | Anchore CVE | High | tomcat-jni-9.0.84 |
CVE-2022-41704 | Anchore CVE | High | org.apache.batik.parser-1.14.0-SNAPSHOT |
CVE-2016-5425 | Anchore CVE | High | tomcat-coyote-9.0.84 |
CVE-2022-26336 | Anchore CVE | Medium | org.apache.poi.ooxml-4.1.1-SNAPSHOT |
CVE-2022-41704 | Anchore CVE | High | org.apache.batik.dom.svg-1.14.0-SNAPSHOT |
CVE-2020-27225 | Anchore CVE | High | org.eclipse.core.expressions-3.9.0 |
CVE-2016-5425 | Anchore CVE | High | tomcat-dbcp-9.0.84 |
CVE-2016-5425 | Anchore CVE | High | tomcat-util-scan-9.0.84 |
CVE-2022-41704 | Anchore CVE | High | org.apache.batik.ext-1.14.0-SNAPSHOT |
CVE-2022-26336 | Anchore CVE | Medium | org.apache.poi-4.1.1-SNAPSHOT |
CVE-2016-5425 | Anchore CVE | High | tomcat-juli-9.0.84 |
CVE-2016-5425 | Anchore CVE | High | tomcat-websocket-9.0.84 |
CVE-2016-5425 | Anchore CVE | High | tomcat-i18n-zh-CN-9.0.84 |
CVE-2016-6325 | Anchore CVE | High | tomcat-i18n-zh-CN-9.0.84 |
CVE-2020-27225 | Anchore CVE | High | org.eclipse.core.commands-3.11.0 |
CVE-2016-6325 | Anchore CVE | High | tomcat-i18n-cs-9.0.84 |
CVE-2022-42890 | Anchore CVE | High | org.apache.batik.dom.svg-1.14.0-SNAPSHOT |
CVE-2016-6325 | Anchore CVE | High | tomcat-i18n-ko-9.0.84 |
CVE-2016-6325 | Anchore CVE | High | tomcat-websocket-9.0.84 |
CVE-2022-41704 | Anchore CVE | High | org.apache.batik.constants-1.14.0-SNAPSHOT |
CVE-2016-6325 | Anchore CVE | High | tomcat-dbcp-9.0.84 |
CVE-2016-6325 | Anchore CVE | High | tomcat-util-9.0.84 |
CVE-2016-5425 | Anchore CVE | High | tomcat-i18n-ko-9.0.84 |
CVE-2020-27225 | Anchore CVE | High | org.eclipse.equinox.preferences-3.10.200 |
GHSA-9gp8-6cg8-7h34 | Anchore CVE | Medium | spring-security-config-5.8.5 |
CVE-2022-41704 | Anchore CVE | High | org.apache.batik.svggen-1.14.0-SNAPSHOT |
CVE-2016-6325 | Anchore CVE | High | tomcat-i18n-de-9.0.84 |
CVE-2020-27225 | Anchore CVE | High | org.eclipse.core.runtime-3.27.0 |
CVE-2022-42890 | Anchore CVE | High | org.apache.batik.css-1.14.0-SNAPSHOT |
CVE-2022-41704 | Anchore CVE | High | org.apache.batik.gvt-1.14.0-SNAPSHOT |
CVE-2022-41704 | Anchore CVE | High | org.apache.batik.awt.util-1.14.0-SNAPSHOT |
CVE-2022-42890 | Anchore CVE | High | org.apache.batik.ext-1.14.0-SNAPSHOT |
CVE-2020-27225 | Anchore CVE | High | org.eclipse.core.resources-3.19.0 |
GHSA-ccgv-vj62-xf9h | Anchore CVE | High | spring-web-5.3.29 |
CVE-2016-6325 | Anchore CVE | High | tomcat-i18n-ja-9.0.84 |
CVE-2020-27225 | Anchore CVE | High | org.eclipse.equinox.common-3.18.0 |
CVE-2016-6325 | Anchore CVE | High | tomcat-coyote-9.0.84 |
CVE-2016-5425 | Anchore CVE | High | tomcat-i18n-pt-BR-9.0.84 |
CVE-2016-6325 | Anchore CVE | High | tomcat-i18n-pt-BR-9.0.84 |
CVE-2016-5425 | Anchore CVE | High | tomcat-i18n-cs-9.0.84 |
CVE-2022-41704 | Anchore CVE | High | org.apache.batik.transcoder-1.14.0-SNAPSHOT |
GHSA-7w75-32cg-r6g2 | Anchore CVE | Medium | tomcat-coyote-9.0.84 |
CVE-2022-42890 | Anchore CVE | High | org.apache.batik.util-1.14.0-SNAPSHOT |
CVE-2022-42890 | Anchore CVE | High | org.apache.batik.awt.util-1.14.0-SNAPSHOT |
CVE-2016-6325 | Anchore CVE | High | tomcat-i18n-fr-9.0.84 |
GHSA-f3jh-qvm4-mg39 | Anchore CVE | High | spring-security-core-5.8.5 |
GHSA-4h8f-2wvx-gg5w | Anchore CVE | Low | bcprov-jdk18on-1.76 |
GHSA-4h8f-2wvx-gg5w | Anchore CVE | Low | bcprov-jdk18on-1.76 |
GHSA-4h8f-2wvx-gg5w | Anchore CVE | Low | bcprov-jdk18on-1.76 |
GHSA-4h8f-2wvx-gg5w | Anchore CVE | Low | bcprov-jdk18on-1.76 |
CVE-2024-22262 | Twistlock CVE | High | spring-web-5.3.29 |
CVE-2024-34447 | Twistlock CVE | Low | org.bouncycastle_bcprov-jdk18on-1.76 |
CVE-2023-34042 | Twistlock CVE | Medium | spring-security-core-5.8.5 |
CVE-2024-30171 | Twistlock CVE | Medium | org.bouncycastle_bcpkix-jdk18on-1.76 |
CVE-2024-30171 | Twistlock CVE | Medium | org.bouncycastle_bcprov-jdk18on-1.76 |
CVE-2024-30172 | Twistlock CVE | Medium | org.bouncycastle_bcprov-jdk18on-1.76 |
CVE-2024-30172 | Twistlock CVE | Medium | org.bouncycastle_bcpkix-jdk18on-1.76 |
CVE-2024-29857 | Twistlock CVE | Medium | org.bouncycastle_bcpkix-jdk18on-1.76 |
CVE-2024-29857 | Twistlock CVE | Medium | org.bouncycastle_bcprov-jdk18on-1.76 |
VAT: https://vat.dso.mil/vat/image?imageName=microfocus/fortify/ssc&tag=23.2&branch=master
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=microfocus/fortify/ssc&tag=23.2&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.