-
Notifications
You must be signed in to change notification settings - Fork 61
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
x/vulndb: potential Go vuln in github.com/argoproj/argo-cd: CVE-2022-31102 #517
Labels
excluded: EFFECTIVELY_PRIVATE
This vulnerability exists in a package can be imported, but isn't meant to be outside that module.
Comments
Vulnerability in tool. |
neild
added
excluded: EFFECTIVELY_PRIVATE
This vulnerability exists in a package can be imported, but isn't meant to be outside that module.
and removed
NotGoVuln
labels
Aug 10, 2022
This was referenced Jan 25, 2023
This was referenced Aug 23, 2023
This was referenced Sep 8, 2023
This was referenced Mar 18, 2024
This was referenced May 21, 2024
This was referenced Jun 7, 2024
Change https://go.dev/cl/592768 mentions this issue: |
Change https://go.dev/cl/607220 mentions this issue: |
gopherbot
pushed a commit
that referenced
this issue
Aug 21, 2024
- data/reports/GO-2022-0507.yaml - data/reports/GO-2022-0508.yaml - data/reports/GO-2022-0509.yaml - data/reports/GO-2022-0510.yaml - data/reports/GO-2022-0511.yaml - data/reports/GO-2022-0512.yaml - data/reports/GO-2022-0516.yaml - data/reports/GO-2022-0517.yaml - data/reports/GO-2022-0518.yaml - data/reports/GO-2022-0540.yaml - data/reports/GO-2022-0547.yaml - data/reports/GO-2022-0550.yaml - data/reports/GO-2022-0554.yaml - data/reports/GO-2022-0556.yaml - data/reports/GO-2022-0559.yaml - data/reports/GO-2022-0560.yaml - data/reports/GO-2022-0561.yaml - data/reports/GO-2022-0562.yaml - data/reports/GO-2022-0566.yaml - data/reports/GO-2022-0570.yaml Updates #507 Updates #508 Updates #509 Updates #510 Updates #511 Updates #512 Updates #516 Updates #517 Updates #518 Updates #540 Updates #547 Updates #550 Updates #554 Updates #556 Updates #559 Updates #560 Updates #561 Updates #562 Updates #566 Updates #570 Change-Id: I3197ea86e01d2ed4ae9e7f17dbd7a3e495c903e4 Reviewed-on: https://go-review.googlesource.com/c/vulndb/+/607220 Reviewed-by: Damien Neil <dneil@google.com> Auto-Submit: Tatiana Bradley <tatianabradley@google.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
excluded: EFFECTIVELY_PRIVATE
This vulnerability exists in a package can be imported, but isn't meant to be outside that module.
CVE-2022-31102 references github.com/argoproj/argo-cd, which may be a Go module.
Description:
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. Argo CD starting with 2.3.0 and prior to 2.3.6 and 2.4.5 is vulnerable to a cross-site scripting (XSS) bug which could allow an attacker to inject arbitrary JavaScript in the
/auth/callback
page in a victim's browser. This vulnerability only affects Argo CD instances which have single sign on (SSO) enabled. The exploit also assumes the attacker has 1) access to the API server's encryption key, 2) a method to add a cookie to the victim's browser, and 3) the ability to convince the victim to visit a malicious/auth/callback
link. The vulnerability is classified as low severity because access to the API server's encryption key already grants a high level of access. Exploiting the XSS would allow the attacker to impersonate the victim, but would not grant any privileges which the attacker could not otherwise gain using the encryption key. A patch for this vulnerability has been released in the following Argo CD versions 2.4.5 and 2.3.6. There is currently no known workaround.Links:
See doc/triage.md for instructions on how to triage this report.
The text was updated successfully, but these errors were encountered: