chore(findings): f18-navy-boeing/osee/osee-hsql
Summary
f18-navy-boeing/osee/osee-hsql has 41 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
CVE-2022-42003 | Anchore CVE | High | com.fasterxml.jackson.core.jackson-databind-2.12.1-SNAPSHOT |
CVE-2020-36518 | Anchore CVE | High | com.fasterxml.jackson.core.jackson-databind-2.12.1-SNAPSHOT |
CVE-2022-42004 | Anchore CVE | High | com.fasterxml.jackson.core.jackson-databind-2.12.1-SNAPSHOT |
CVE-2022-46908 | Anchore CVE | High | org.xerial.sqlite-3.40.0.0 |
GHSA-p26g-97m4-6q7c | Anchore CVE | Low | jetty-server-9.4.48.v20220622 |
GHSA-qw69-rqj8-6qw8 | Anchore CVE | Medium | jetty-server-9.4.48.v20220622 |
CVE-2023-26048 | Anchore CVE | Medium | jetty-util-9.4.48.v20220622 |
CVE-2023-26049 | Anchore CVE | Medium | org.eclipse.jetty.security-9.4.48.v20220622 |
CVE-2023-26049 | Anchore CVE | Medium | jetty-util-ajax-9.4.48.v20220622 |
CVE-2023-26049 | Anchore CVE | Medium | org.eclipse.jetty.servlet-9.4.48.v20220622 |
CVE-2023-26048 | Anchore CVE | Medium | org.eclipse.jetty.servlet-9.4.48.v20220622 |
CVE-2023-26048 | Anchore CVE | Medium | org.eclipse.jetty.io-9.4.48.v20220622 |
CVE-2023-26048 | Anchore CVE | Medium | jetty-security-9.4.48.v20220622 |
CVE-2023-26048 | Anchore CVE | Medium | org.eclipse.jetty.security-9.4.48.v20220622 |
CVE-2023-26049 | Anchore CVE | Medium | jetty-util-9.4.48.v20220622 |
CVE-2023-26049 | Anchore CVE | Medium | org.eclipse.jetty.http-9.4.48.v20220622 |
CVE-2023-26048 | Anchore CVE | Medium | jetty-servlet-9.4.48.v20220622 |
CVE-2023-26048 | Anchore CVE | Medium | org.eclipse.jetty.util-9.4.48.v20220622 |
CVE-2023-26048 | Anchore CVE | Medium | org.eclipse.jetty.server-9.4.48.v20220622 |
CVE-2023-26048 | Anchore CVE | Medium | org.eclipse.jetty.util.ajax-9.4.48.v20220622 |
CVE-2023-26049 | Anchore CVE | Medium | org.eclipse.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-http-9.4.48.v20220622 |
CVE-2023-26048 | Anchore CVE | Medium | org.eclipse.jetty.http-9.4.48.v20220622 |
CVE-2023-26049 | Anchore CVE | Medium | org.eclipse.jetty.io-9.4.48.v20220622 |
CVE-2023-26049 | Anchore CVE | Medium | jetty-security-9.4.48.v20220622 |
CVE-2023-26048 | Anchore CVE | Medium | jetty-http-9.4.48.v20220622 |
CVE-2023-26049 | Anchore CVE | Medium | jetty-servlet-9.4.48.v20220622 |
CVE-2023-26049 | Anchore CVE | Medium | org.eclipse.jetty.util-9.4.48.v20220622 |
CVE-2023-26049 | Anchore CVE | Medium | jetty-io-9.4.48.v20220622 |
CVE-2023-26049 | Anchore CVE | Medium | org.eclipse.jetty.util.ajax-9.4.48.v20220622 |
CVE-2023-26048 | Anchore CVE | Medium | jetty-util-ajax-9.4.48.v20220622 |
CVE-2021-46877 | Anchore CVE | High | com.fasterxml.jackson.core.jackson-databind-2.12.1-SNAPSHOT |
GHSA-6phf-6h5g-97j2 | Anchore CVE | High | sqlite-jdbc-3.40.0.0 |
CVE-2023-35116 | Anchore CVE | Medium | com.fasterxml.jackson.core.jackson-databind-2.12.1-SNAPSHOT |
CVE-2023-2976 | Anchore CVE | High | com.google.guava-27.1.0-SNAPSHOT |
CVE-2023-26049 | Twistlock CVE | Low | org.eclipse.jetty_jetty-server-9.4.48 |
CVE-2023-26048 | Twistlock CVE | Medium | org.eclipse.jetty_jetty-server-9.4.48 |
CVE-2023-26049 | Twistlock CVE | Medium | org.eclipse.jetty_jetty-io-9.4.48 |
CVE-2023-26048 | Twistlock CVE | Medium | org.eclipse.jetty_jetty-io-9.4.48 |
CVE-2023-32697 | Twistlock CVE | High | org.xerial_sqlite-jdbc-3.40.0.0 |
VAT: https://vat.dso.mil/vat/image?imageName=f18-navy-boeing/osee/osee-hsql&tag=1.0.0.v20230216&branch=master
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=f18-navy-boeing/osee/osee-hsql&tag=1.0.0.v20230216&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.