You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While packagingopensearch-k8s-operator I noticed a handful of CVEs in current dependency versions. Specially, I came across these CVEs in the noted packages:
📦 golang.org/x/net v0.13.0 (go-module)
High CVE-2023-39325 GHSA-4374-p667-p6c8 fixed in 0.17.0
Medium CVE-2023-45288 GHSA-4v7x-pqxf-cx7m fixed in 0.23.0
Medium CVE-2023-44487 GHSA-qppj-fm5r-hxr3 fixed in 0.17.0
📦 google.golang.org/protobuf v1.30.0 (go-module)
Medium CVE-2024-24786 GHSA-8r3f-844c-mc37 fixed in 1.33.0
There appear to be fixes for all four CVEs available in newer versions of the dependencies. Would the maintainers be amenable to a PR to bump these dependencies (or all dependencies, in fact) to the newest version?
The text was updated successfully, but these errors were encountered:
While packaging
opensearch-k8s-operator
I noticed a handful of CVEs in current dependency versions. Specially, I came across these CVEs in the noted packages:There appear to be fixes for all four CVEs available in newer versions of the dependencies. Would the maintainers be amenable to a PR to bump these dependencies (or all dependencies, in fact) to the newest version?
The text was updated successfully, but these errors were encountered: