chore(findings): frontiertechnology/cortex/authentication-api
Summary
frontiertechnology/cortex/authentication-api has 15 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
GHSA-qrmm-w75w-3wpx | Anchore CVE | Medium | Swashbuckle.AspNetCore.SwaggerUI-6.2.1 |
GHSA-ghhp-997w-qr28 | Anchore CVE | Critical | System.Text.Encodings.Web-4.7.0 |
GHSA-59j7-ghrg-fj52 | Anchore CVE | Medium | Microsoft.IdentityModel.JsonWebTokens-5.6.0.61018232319.2574f3cbc3736db085497b9b241ea5ae338357b9 |
GHSA-59j7-ghrg-fj52 | Anchore CVE | Medium | System.IdentityModel.Tokens.Jwt-5.6.0.61018232319.2574f3cbc3736db085497b9b241ea5ae338357b9 |
GHSA-qrmm-w75w-3wpx | Anchore CVE | Medium | Swashbuckle.AspNetCore.SwaggerUI-6.2.1.0 |
GHSA-59j7-ghrg-fj52 | Anchore CVE | Medium | System.IdentityModel.Tokens.Jwt-5.6.0 |
GHSA-59j7-ghrg-fj52 | Anchore CVE | Medium | Microsoft.IdentityModel.JsonWebTokens-5.6.0 |
GHSA-5crp-9r3c-p9vr | Anchore CVE | High | Newtonsoft.Json-12.0.2 |
GHSA-vh55-786g-wjwj | Anchore CVE | Medium | System.Security.Cryptography.Xml-5.0.0.0 |
CCE-83623-9 | OSCAP Compliance | Medium | |
CVE-2021-26701 | Twistlock CVE | Critical | system.text.encodings.web-4.7.0 |
CVE-2024-21907 | Twistlock CVE | High | newtonsoft.json-12.0.2 |
CVE-2024-21319 | Twistlock CVE | Medium | system.identitymodel.tokens.jwt-5.6.0 |
CVE-2024-21319 | Twistlock CVE | Medium | microsoft.identitymodel.jsonwebtokens-5.6.0 |
GHSA-qrmm-w75w-3wpx | Twistlock CVE | Medium | swashbuckle.aspnetcore.swaggerui-6.2.1 |
VAT: https://vat.dso.mil/vat/image?imageName=frontiertechnology/cortex/authentication-api&tag=v1.3&branch=master
More information can be found in the failed pipeline located here: https://repo1.dso.mil/dsop/frontiertechnology/cortex/authentication-api/-/jobs/22721527
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.