chore(findings): mitre/saf/inspec_tools
Summary
mitre/saf/inspec_tools has 95 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
CVE-2021-41098 | Twistlock CVE | High | nokogiri-1.12.3 |
GHSA-2rr5-8q37-2w7h | Anchore CVE | High | nokogiri-1.12.3 |
CVE-2021-34831 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2021-34850 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2021-34832 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2021-34839 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2021-38566 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2021-34852 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2021-34846 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2021-34849 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2021-34835 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2021-34842 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2021-34848 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2021-38567 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2021-38565 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2021-34838 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2021-34836 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2021-34844 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2021-34837 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2021-38564 | Anchore CVE | Critical | pdf-reader-2.5.0 |
CVE-2021-34851 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2021-45978 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2021-34833 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2021-34840 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2021-34841 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2021-34845 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2021-38563 | Anchore CVE | Critical | pdf-reader-2.5.0 |
CVE-2021-34847 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2021-45980 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2021-34853 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2021-45979 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2013-0732 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2021-34834 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2021-34843 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2021-30560 | Twistlock CVE | High | nokogiri-1.12.3 |
CVE-2022-24357 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2022-24360 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2022-24364 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2022-24359 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2022-24365 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2022-24362 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2022-24971 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2022-24368 | Anchore CVE | Medium | pdf-reader-2.5.0 |
CVE-2022-24356 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2022-24369 | Anchore CVE | High | pdf-reader-2.5.0 |
GHSA-fq42-c5rg-92c2 | Anchore CVE | High | nokogiri-1.12.3 |
CVE-2022-24367 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2022-24366 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2022-24370 | Anchore CVE | Medium | pdf-reader-2.5.0 |
CVE-2022-24361 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2022-24363 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2022-24954 | Anchore CVE | Critical | pdf-reader-2.5.0 |
CVE-2022-24358 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2022-24955 | Anchore CVE | Critical | pdf-reader-2.5.0 |
CVE-2022-25108 | Anchore CVE | Medium | pdf-reader-2.5.0 |
GHSA-xxx9-3xcr-gjj3 | Anchore CVE | Medium | nokogiri-1.12.3 |
GHSA-gx8x-g87m-h5q6 | Anchore CVE | High | nokogiri-1.12.3 |
GHSA-v6gp-9mmm-c6p5 | Anchore CVE | High | nokogiri-1.12.3 |
GHSA-crjr-9rc5-ghw8 | Anchore CVE | High | nokogiri-1.12.3 |
CVE-2018-25032 | Twistlock CVE | High | nokogiri-1.12.3 |
CVE-2022-23437 | Twistlock CVE | Medium | nokogiri-1.12.3 |
CVE-2022-24839 | Twistlock CVE | High | nokogiri-1.12.3 |
CVE-2022-24836 | Twistlock CVE | High | nokogiri-1.12.3 |
GHSA-cgx6-hpwq-fhv5 | Anchore CVE | High | nokogiri-1.12.3 |
CVE-2022-30557 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2022-29181 | Twistlock CVE | High | nokogiri-1.12.3 |
GHSA-xh29-r2w5-wx8m | Anchore CVE | High | nokogiri-1.12.3 |
GHSA-5c5f-7vfq-3732 | Anchore CVE | Critical | jmespath-1.4.0 |
CVE-2022-32511 | Twistlock CVE | Critical | jmespath-1.4.0 |
CVE-2022-28674 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2022-28682 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2022-28670 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2022-28677 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2022-28676 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2022-28681 | Anchore CVE | Medium | pdf-reader-2.5.0 |
CVE-2022-28675 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2022-28683 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2022-34875 | Anchore CVE | Low | pdf-reader-2.5.0 |
CVE-2022-28678 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2022-34873 | Anchore CVE | Low | pdf-reader-2.5.0 |
CVE-2022-28671 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2022-28669 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2022-28672 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2022-28679 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2022-34874 | Anchore CVE | Low | pdf-reader-2.5.0 |
CVE-2022-28673 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2022-26979 | Anchore CVE | High | pdf-reader-2.5.0 |
CVE-2022-27944 | Anchore CVE | High | pdf-reader-2.5.0 |
GHSA-2qc6-mcvw-92cw | Anchore CVE | Medium | nokogiri-1.12.3 |
CVE-2022-27359 | Anchore CVE | Medium | pdf-reader-2.5.0 |
GHSA-j6gc-792m-qgm2 | Anchore CVE | Low | activesupport-6.1.4 |
CVE-2023-22796 | Twistlock CVE | High | activesupport-6.1.4 |
CVE-2022-47881 | Anchore CVE | Medium | pdf-reader-2.5.0 |
GHSA-pj73-v5mw-pm9j | Anchore CVE | Medium | activesupport-6.1.4 |
CVE-2023-28120 | Twistlock CVE | Low | activesupport-6.1.4 |
VAT: https://vat.dso.mil/vat/image?imageName=mitre/saf/inspec_tools&tag=3.1.0&branch=master
More information can be found in the failed pipeline located here: https://repo1.dso.mil/dsop/mitre/saf/inspec_tools/-/jobs/12417009
Tasks
Contributor:
-
Provide justifications for findings in the VAT (docs) -
Apply the ~"Approval" label to this issue and wait for feedback
Iron Bank:
-
Review findings and justifications -
Send approval request to Authorizing Official -
Close issue after approval from Authorizing Official
Note: If the above approval process is rejected for any reason, the
Approval
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 theApproval
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.