Skip to content

fix: Ensure both priave ca certs configmaps have default names (#304) #67

fix: Ensure both priave ca certs configmaps have default names (#304)

fix: Ensure both priave ca certs configmaps have default names (#304) #67

GitHub Actions / forge-k8s:main-linux-arm64 scan results succeeded Feb 8, 2024 in 0s

1 fail in 0s

1 tests   0 ✅  0s ⏱️
4 suites  0 💤
1 files    1 ❌

Results for commit b3cd583.

Annotations

Check warning on line 0 in tough-cookie-2.5.0

See this annotation in the file changed.

@github-actions github-actions / forge-k8s:main-linux-arm64 scan results

[MEDIUM] CVE-2023-26136 (tough-cookie-2.5.0) failed

trivy-junit-results.xml
Raw output
tough-cookie: prototype pollution in cookie memstore
Versions of the package tough-cookie before 4.1.3 are vulnerable to Prototype Pollution due to improper handling of Cookies when using CookieJar in rejectPublicSuffixes=false mode. This issue arises from the manner in which the objects are initialized.

Check notice on line 0 in .github

See this annotation in the file changed.

@github-actions github-actions / forge-k8s:main-linux-arm64 scan results

1 test found

There is 1 test, see "Raw output" for the name of the test.
Raw output
tough-cookie-2.5.0 ‑ [MEDIUM] CVE-2023-26136