chore(findings): spearhp/frontend
Summary
spearhp/frontend has 43 new findings discovered during continuous monitoring.
id | source | severity | package |
---|---|---|---|
GHSA-g85r-6x2q-45w7 | Anchore CVE | Medium | SixLabors.ImageSharp-2.1.3.0 |
GHSA-59j7-ghrg-fj52 | Anchore CVE | Medium | System.IdentityModel.Tokens.Jwt-6.21.0 |
GHSA-98g6-xh36-x2p7 | Anchore CVE | High | Microsoft.Data.SqlClient-5.0.0.0 |
GHSA-98g6-xh36-x2p7 | Anchore CVE | High | System.Data.SqlClient-4.4.0 |
GHSA-5mfx-4wcx-rv27 | Anchore CVE | High | Azure.Identity-1.6.0 |
GHSA-8g2p-5pqh-5jmc | Anchore CVE | Medium | System.Data.SqlClient-4.6.25519.03 |
GHSA-98g6-xh36-x2p7 | Anchore CVE | High | Microsoft.Data.SqlClient-5.0.0.0 |
GHSA-5x7m-6737-26cr | Anchore CVE | Medium | SixLabors.ImageSharp-2.1.3 |
GHSA-98g6-xh36-x2p7 | Anchore CVE | High | System.Data.SqlClient-4.6.25519.03 |
GHSA-g85r-6x2q-45w7 | Anchore CVE | Medium | SixLabors.ImageSharp-2.1.3 |
GHSA-8g2p-5pqh-5jmc | Anchore CVE | Medium | System.Data.SqlClient-4.4.0 |
GHSA-cmhx-cq75-c4mj | Anchore CVE | High | System.Text.RegularExpressions-4.3.0 |
GHSA-59j7-ghrg-fj52 | Anchore CVE | Medium | System.IdentityModel.Tokens.Jwt-6.21.0.30701180446.3ba3685a8eb8b1a912c4b46c87a6583133c5d721 |
GHSA-8g2p-5pqh-5jmc | Anchore CVE | Medium | System.Data.SqlClient-4.6.25519.03 |
GHSA-wvxc-855f-jvrv | Anchore CVE | Medium | Azure.Identity-1.6.0 |
GHSA-98g6-xh36-x2p7 | Anchore CVE | High | Microsoft.Data.SqlClient-5.0.0.0 |
GHSA-98g6-xh36-x2p7 | Anchore CVE | High | System.Data.SqlClient-4.6.25519.03 |
GHSA-c3hf-8vgx-72rh | Anchore CVE | High | System.Net.Requests-6.0.0.0 |
GHSA-65x7-c272-7g7r | Anchore CVE | High | SixLabors.ImageSharp-2.1.3.0 |
GHSA-5x7m-6737-26cr | Anchore CVE | Medium | SixLabors.ImageSharp-2.1.3.0 |
GHSA-59j7-ghrg-fj52 | Anchore CVE | Medium | Microsoft.IdentityModel.JsonWebTokens-6.21.0 |
GHSA-vh55-786g-wjwj | Anchore CVE | Medium | System.Security.Cryptography.Xml-5.0.0 |
GHSA-65x7-c272-7g7r | Anchore CVE | High | SixLabors.ImageSharp-2.1.3 |
GHSA-3fx3-85r4-8j3w | Anchore CVE | Medium | Microsoft.AspNetCore.Components-6.0.0.0 |
GHSA-98g6-xh36-x2p7 | Anchore CVE | High | System.Data.SqlClient-4.6.25519.03 |
GHSA-98g6-xh36-x2p7 | Anchore CVE | High | System.Data.SqlClient-4.6.25519.03 |
GHSA-59j7-ghrg-fj52 | Anchore CVE | Medium | Microsoft.IdentityModel.JsonWebTokens-6.21.0.30701180446.3ba3685a8eb8b1a912c4b46c87a6583133c5d721 |
GHSA-98g6-xh36-x2p7 | Anchore CVE | High | Microsoft.Data.SqlClient-5.0.0.0 |
GHSA-98g6-xh36-x2p7 | Anchore CVE | High | Microsoft.Data.SqlClient-5.0.0 |
GHSA-8g2p-5pqh-5jmc | Anchore CVE | Medium | System.Data.SqlClient-4.6.25519.03 |
GHSA-8g2p-5pqh-5jmc | Anchore CVE | Medium | System.Data.SqlClient-4.6.25519.03 |
CVE-2023-36414 | Twistlock CVE | High | azure.identity-1.6.0 |
CVE-2024-0056 | Twistlock CVE | High | system.data.sqlclient-4.4.0 |
CVE-2024-0056 | Twistlock CVE | High | microsoft.data.sqlclient-5.0.0 |
CVE-2019-0820 | Twistlock CVE | High | system.text.regularexpressions-4.3.0 |
CVE-2024-21319 | Twistlock CVE | Medium | microsoft.identitymodel.jsonwebtokens-6.21.0 |
CVE-2024-21319 | Twistlock CVE | Medium | system.identitymodel.tokens.jwt-6.21.0 |
CVE-2022-34716 | Twistlock CVE | Medium | system.security.cryptography.xml-5.0.0 |
CVE-2022-41064 | Twistlock CVE | Medium | system.data.sqlclient-4.4.0 |
CVE-2024-27929 | Twistlock CVE | High | sixlabors.imagesharp-2.1.3 |
CVE-2024-29992 | Twistlock CVE | Medium | azure.identity-1.6.0 |
CVE-2024-32036 | Twistlock CVE | Medium | sixlabors.imagesharp-2.1.3 |
CVE-2024-32035 | Twistlock CVE | Medium | sixlabors.imagesharp-2.1.3 |
VAT: https://vat.dso.mil/vat/image?imageName=spearhp/frontend&tag=1.0.2&branch=master
More information can be found in the VAT located here: https://vat.dso.mil/vat/image?imageName=spearhp/frontend&tag=1.0.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.