chore(findings): opensensorhub/socom-osh-node
Summary
opensensorhub/socom-osh-node has 144 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
GHSA-qw69-rqj8-6qw8 | Anchore CVE | Medium | jetty-server-9.4.48.v20220622 |
GHSA-p26g-97m4-6q7c | Anchore CVE | Low | jetty-server-9.4.48.v20220622 |
CVE-2023-26048 | Anchore CVE | Medium | jetty-io-9.4.48.v20220622 |
CVE-2023-26049 | Anchore CVE | Medium | jetty-continuation-9.4.48.v20220622 |
CVE-2023-26049 | Anchore CVE | Medium | jetty-io-9.4.48.v20220622 |
CVE-2023-26049 | Anchore CVE | Medium | jetty-xml-9.4.48.v20220622 |
CVE-2023-26049 | Anchore CVE | Medium | jetty-util-9.4.48.v20220622 |
CVE-2023-26048 | Anchore CVE | Medium | jetty-servlet-9.4.48.v20220622 |
CVE-2023-26049 | Anchore CVE | Medium | jetty-security-9.4.48.v20220622 |
CVE-2023-26048 | Anchore CVE | Medium | jetty-security-9.4.48.v20220622 |
CVE-2023-26048 | Anchore CVE | Medium | jetty-xml-9.4.48.v20220622 |
CVE-2023-26049 | Anchore CVE | Medium | jetty-http-9.4.48.v20220622 |
CVE-2023-26048 | Anchore CVE | Medium | jetty-util-ajax-9.4.48.v20220622 |
CVE-2023-26049 | Anchore CVE | Medium | jetty-client-9.4.48.v20220622 |
CVE-2023-26049 | Anchore CVE | Medium | jetty-servlet-9.4.48.v20220622 |
CVE-2023-26048 | Anchore CVE | Medium | jetty-http-9.4.48.v20220622 |
CVE-2023-26048 | Anchore CVE | Medium | jetty-servlets-9.4.48.v20220622 |
CVE-2023-26048 | Anchore CVE | Medium | jetty-client-9.4.48.v20220622 |
CVE-2023-26049 | Anchore CVE | Medium | jetty-util-ajax-9.4.48.v20220622 |
CVE-2023-26048 | Anchore CVE | Medium | jetty-continuation-9.4.48.v20220622 |
CVE-2023-26048 | Anchore CVE | Medium | jetty-util-9.4.48.v20220622 |
CVE-2023-26049 | Anchore CVE | Medium | jetty-servlets-9.4.48.v20220622 |
CVE-2023-2618 | Anchore CVE | High | opencv-4.6.0-1.5.8 |
CVE-2023-2617 | Anchore CVE | High | opencv-4.6.0-1.5.8 |
CVE-2023-2617 | Anchore CVE | High | opencv-4.6.0-1.5.8 |
CVE-2023-2617 | Anchore CVE | High | opencv-4.6.0-1.5.8 |
CVE-2023-2618 | Anchore CVE | High | opencv-4.6.0-1.5.8 |
CVE-2023-2618 | Anchore CVE | High | opencv-4.6.0-1.5.8 |
CVE-2023-2618 | Anchore CVE | High | opencv-4.6.0-1.5.8 |
CVE-2023-2617 | Anchore CVE | High | opencv-4.6.0-1.5.8 |
CVE-2023-2617 | Anchore CVE | High | opencv-4.6.0-1.5.8 |
CVE-2023-2618 | Anchore CVE | High | opencv-4.6.0-1.5.8 |
CVE-2023-32303 | Anchore CVE | Medium | sensorhub-driver-planet-skysat-video-0.1.0 |
GHSA-7g45-4rm6-3mm3 | Anchore CVE | Medium | guava-31.1-jre |
GHSA-6mjq-h674-j845 | Anchore CVE | Medium | netty-handler-4.1.90.Final |
CVE-2023-35116 | Anchore CVE | Medium | jackson-databind-2.13.4.2 |
GHSA-58qw-p7qm-5rvh | Anchore CVE | Low | jetty-xml-9.4.48.v20220622 |
GHSA-5mg8-w23w-74h3 | Anchore CVE | Low | guava-31.1-jre |
GHSA-3gh6-v5v9-6v9j | Anchore CVE | Low | jetty-servlets-9.4.48.v20220622 |
GHSA-hmr7-m48g-48f6 | Anchore CVE | Medium | jetty-http-9.4.48.v20220622 |
CVE-2023-41900 | Anchore CVE | Medium | jetty-client-9.4.48.v20220622 |
CVE-2023-40167 | Anchore CVE | Medium | jetty-security-9.4.48.v20220622 |
CVE-2023-41900 | Anchore CVE | Medium | jetty-http-9.4.48.v20220622 |
CVE-2023-36479 | Anchore CVE | Medium | jetty-io-9.4.48.v20220622 |
CVE-2023-40167 | Anchore CVE | Medium | jetty-servlets-9.4.48.v20220622 |
CVE-2023-36479 | Anchore CVE | Medium | jetty-servlet-9.4.48.v20220622 |
CVE-2023-36479 | Anchore CVE | Medium | jetty-http-9.4.48.v20220622 |
CVE-2023-40167 | Anchore CVE | Medium | jetty-xml-9.4.48.v20220622 |
CVE-2023-40167 | Anchore CVE | Medium | jetty-client-9.4.48.v20220622 |
CVE-2023-36479 | Anchore CVE | Medium | jetty-continuation-9.4.48.v20220622 |
CVE-2023-41900 | Anchore CVE | Medium | jetty-servlet-9.4.48.v20220622 |
CVE-2023-36479 | Anchore CVE | Medium | jetty-server-9.4.48.v20220622 |
CVE-2023-41900 | Anchore CVE | Medium | jetty-io-9.4.48.v20220622 |
CVE-2023-40167 | Anchore CVE | Medium | jetty-servlet-9.4.48.v20220622 |
CVE-2023-41900 | Anchore CVE | Medium | jetty-security-9.4.48.v20220622 |
CVE-2023-36479 | Anchore CVE | Medium | jetty-security-9.4.48.v20220622 |
CVE-2023-41900 | Anchore CVE | Medium | jetty-servlets-9.4.48.v20220622 |
CVE-2023-40167 | Anchore CVE | Medium | jetty-io-9.4.48.v20220622 |
CVE-2023-40167 | Anchore CVE | Medium | jetty-server-9.4.48.v20220622 |
CVE-2023-40167 | Anchore CVE | Medium | jetty-util-ajax-9.4.48.v20220622 |
CVE-2023-40167 | Anchore CVE | Medium | jetty-util-9.4.48.v20220622 |
CVE-2023-41900 | Anchore CVE | Medium | jetty-xml-9.4.48.v20220622 |
CVE-2023-36479 | Anchore CVE | Medium | jetty-xml-9.4.48.v20220622 |
CVE-2023-36479 | Anchore CVE | Medium | jetty-client-9.4.48.v20220622 |
CVE-2023-41900 | Anchore CVE | Medium | jetty-util-9.4.48.v20220622 |
CVE-2023-41900 | Anchore CVE | Medium | jetty-server-9.4.48.v20220622 |
CVE-2023-41900 | Anchore CVE | Medium | jetty-continuation-9.4.48.v20220622 |
CVE-2023-40167 | Anchore CVE | Medium | jetty-continuation-9.4.48.v20220622 |
CVE-2023-41900 | Anchore CVE | Medium | jetty-util-ajax-9.4.48.v20220622 |
CVE-2023-36479 | Anchore CVE | Medium | jetty-util-ajax-9.4.48.v20220622 |
CVE-2023-36479 | Anchore CVE | Medium | jetty-util-9.4.48.v20220622 |
CVE-2023-44487 | Anchore CVE | High | jetty-xml-9.4.48.v20220622 |
CVE-2023-44487 | Anchore CVE | High | jetty-server-9.4.48.v20220622 |
CVE-2023-44487 | Anchore CVE | High | jetty-client-9.4.48.v20220622 |
CVE-2023-44487 | Anchore CVE | High | jetty-io-9.4.48.v20220622 |
CVE-2023-44487 | Anchore CVE | High | jetty-continuation-9.4.48.v20220622 |
CVE-2023-44487 | Anchore CVE | High | jetty-servlet-9.4.48.v20220622 |
CVE-2023-44487 | Anchore CVE | High | jetty-util-9.4.48.v20220622 |
CVE-2023-44487 | Anchore CVE | High | jetty-util-ajax-9.4.48.v20220622 |
CVE-2023-44487 | Anchore CVE | High | jetty-http-9.4.48.v20220622 |
CVE-2023-44487 | Anchore CVE | High | jetty-servlets-9.4.48.v20220622 |
CVE-2023-44487 | Anchore CVE | High | jetty-security-9.4.48.v20220622 |
CVE-2023-36478 | Anchore CVE | High | jetty-util-9.4.48.v20220622 |
CVE-2023-36478 | Anchore CVE | High | jetty-io-9.4.48.v20220622 |
CVE-2023-36478 | Anchore CVE | High | jetty-servlet-9.4.48.v20220622 |
CVE-2023-36478 | Anchore CVE | High | jetty-security-9.4.48.v20220622 |
CVE-2023-36478 | Anchore CVE | High | jetty-http-9.4.48.v20220622 |
CVE-2023-36478 | Anchore CVE | High | jetty-server-9.4.48.v20220622 |
CVE-2023-36478 | Anchore CVE | High | jetty-xml-9.4.48.v20220622 |
CVE-2023-36478 | Anchore CVE | High | jetty-continuation-9.4.48.v20220622 |
CVE-2023-36478 | Anchore CVE | High | jetty-servlets-9.4.48.v20220622 |
CVE-2023-36478 | Anchore CVE | High | jetty-util-ajax-9.4.48.v20220622 |
CVE-2023-36478 | Anchore CVE | High | jetty-client-9.4.48.v20220622 |
CVE-2023-46407 | Anchore CVE | Medium | ffmpeg-5.1.2-1.5.8 |
CVE-2023-46407 | Anchore CVE | Medium | ffmpeg-5.1.2-1.5.8 |
CVE-2023-46407 | Anchore CVE | Medium | ffmpeg-5.1.2-1.5.8 |
CVE-2023-46407 | Anchore CVE | Medium | ffmpeg-5.1.2-1.5.8 |
CVE-2023-46407 | Anchore CVE | Medium | ffmpeg-5.1.2-1.5.8 |
CVE-2023-47470 | Anchore CVE | High | ffmpeg-5.1.2-1.5.8 |
CVE-2023-47470 | Anchore CVE | High | ffmpeg-5.1.2-1.5.8 |
GHSA-vmq6-5m68-f53m | Anchore CVE | High | logback-classic-1.2.11 |
CVE-2023-47470 | Anchore CVE | High | ffmpeg-5.1.2-1.5.8 |
GHSA-vmq6-5m68-f53m | Anchore CVE | High | logback-core-1.2.11 |
CVE-2023-47470 | Anchore CVE | High | ffmpeg-5.1.2-1.5.8 |
CVE-2023-47470 | Anchore CVE | High | ffmpeg-5.1.2-1.5.8 |
CVE-2024-22862 | Anchore CVE | Critical | ffmpeg-5.1.2-1.5.8 |
CVE-2024-22860 | Anchore CVE | Critical | ffmpeg-5.1.2-1.5.8 |
CVE-2024-22861 | Anchore CVE | High | ffmpeg-5.1.2-1.5.8 |
CVE-2024-22862 | Anchore CVE | Critical | ffmpeg-5.1.2-1.5.8 |
CVE-2024-22861 | Anchore CVE | High | ffmpeg-5.1.2-1.5.8 |
CVE-2024-22860 | Anchore CVE | Critical | ffmpeg-5.1.2-1.5.8 |
CVE-2024-22862 | Anchore CVE | Critical | ffmpeg-5.1.2-1.5.8 |
CVE-2024-22860 | Anchore CVE | Critical | ffmpeg-5.1.2-1.5.8 |
CVE-2024-22862 | Anchore CVE | Critical | ffmpeg-5.1.2-1.5.8 |
CVE-2024-22861 | Anchore CVE | High | ffmpeg-5.1.2-1.5.8 |
CVE-2024-22861 | Anchore CVE | High | ffmpeg-5.1.2-1.5.8 |
CVE-2024-22860 | Anchore CVE | Critical | ffmpeg-5.1.2-1.5.8 |
CVE-2024-22861 | Anchore CVE | High | ffmpeg-5.1.2-1.5.8 |
CVE-2024-22860 | Anchore CVE | Critical | ffmpeg-5.1.2-1.5.8 |
CVE-2024-22862 | Anchore CVE | Critical | ffmpeg-5.1.2-1.5.8 |
CVE-2022-0529 | Anchore CVE | Low | unzip-6.0-46.el8 |
CVE-2022-0530 | Anchore CVE | Low | unzip-6.0-46.el8 |
GHSA-wjxj-5m7g-mg7q | Anchore CVE | Medium | bcprov-jdk15on-1.69 |
CVE-2021-4217 | Anchore CVE | Low | unzip-6.0-46.el8 |
GHSA-hr8g-6v94-x4m9 | Anchore CVE | Medium | bcprov-jdk15on-1.69 |
CVE-2023-33201 | Twistlock CVE | Medium | org.bouncycastle_bcprov-jdk15on-1.69 |
CVE-2023-6378 | Twistlock CVE | High | ch.qos.logback_logback-classic-1.2.11 |
CVE-2023-34462 | Twistlock CVE | Medium | io.netty_netty-handler-4.1.90.Final |
CVE-2023-40167 | Twistlock CVE | Medium | org.eclipse.jetty_jetty-http-9.4.48.v20220622 |
CVE-2023-26048 | Twistlock CVE | Medium | org.eclipse.jetty_jetty-server-9.4.48.v20220622 |
GHSA-58qw-p7qm-5rvh | Twistlock CVE | Low | org.eclipse.jetty_jetty-xml-9.4.48.v20220622 |
CVE-2023-36479 | Twistlock CVE | Low | org.eclipse.jetty_jetty-servlets-9.4.48.v20220622 |
CVE-2023-26049 | Twistlock CVE | Low | org.eclipse.jetty_jetty-server-9.4.48.v20220622 |
CVE-2023-33202 | Twistlock CVE | Medium | org.bouncycastle_bcprov-jdk15on-1.69 |
CVE-2023-6378 | Twistlock CVE | High | ch.qos.logback_logback-core-1.2.11 |
CVE-2023-44487 | Twistlock CVE | High | org.eclipse.jetty_jetty-io-9.4.48.v20220622 |
CVE-2023-36478 | Twistlock CVE | High | org.eclipse.jetty_jetty-io-9.4.48.v20220622 |
CVE-2023-2976 | Twistlock CVE | High | com.google.guava_guava-31.1-jre |
CVE-2023-40167 | Twistlock CVE | Medium | org.eclipse.jetty_jetty-io-9.4.48.v20220622 |
CVE-2023-26049 | Twistlock CVE | Medium | org.eclipse.jetty_jetty-io-9.4.48.v20220622 |
CVE-2023-26048 | Twistlock CVE | Medium | org.eclipse.jetty_jetty-io-9.4.48.v20220622 |
CVE-2023-41900 | Twistlock CVE | Medium | org.eclipse.jetty_jetty-io-9.4.48.v20220622 |
CVE-2023-36479 | Twistlock CVE | Medium | org.eclipse.jetty_jetty-io-9.4.48.v20220622 |
CVE-2020-8908 | Twistlock CVE | Low | com.google.guava_guava-31.1-jre |
VAT: https://vat.dso.mil/vat/image?imageName=opensensorhub/socom-osh-node&tag=2.0.2&branch=master
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=opensensorhub/socom-osh-node&tag=2.0.2&branch=master
Tasks
Contributor:
-
Provide justifications for findings in the VAT (docs) -
Apply the ~"Hardening::Verification" 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.