Skip to content

x/vulndb: suggestion regarding GO-2025-3427 #3464

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
svghadi opened this issue Feb 13, 2025 · 2 comments
Closed

x/vulndb: suggestion regarding GO-2025-3427 #3464

svghadi opened this issue Feb 13, 2025 · 2 comments

Comments

@svghadi
Copy link

svghadi commented Feb 13, 2025

Report ID

GO-2025-3427

Suggestion/Comment

The CVE was incorrectly tagged to ArgoCD. It is actually affecting RedHat's implementation of ArgoCD which is RedHat OpenShift GitOps. The original report is fixed. Please update accordingly.
Ref: https://access.redhat.com/security/cve/CVE-2024-13484

Affected Source: https://github.com/redhat-developer/gitops-operator
Affected Version: <=1.15.0
Patched Version: Unknown

@thatnealpatel
Copy link
Member

Thank you for the suggestion @svghadi

@gopherbot
Copy link
Contributor

Change https://go.dev/cl/657635 mentions this issue: data/reports: update GO-2025-3427

gopherbot pushed a commit that referenced this issue Mar 13, 2025
  - data/reports/GO-2025-3427.yaml

Updates #3427
Updates #3464

Change-Id: Ibfb17adc86b1ac85c5182d93a84abfbbe5b465bd
Reviewed-on: https://go-review.googlesource.com/c/vulndb/+/657635
Reviewed-by: Zvonimir Pavlinovic <[email protected]>
LUCI-TryBot-Result: Go LUCI <[email protected]>
Auto-Submit: Neal Patel <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants