NetSight

Security Dashboard

A live picture of new vulnerabilities, flaws exploited in the wild and malicious packages.

Reset
87 matching advisories · page 2 of 3Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.7 CVE-2024-47827 Argo Workflows Controller: Denial of Service via malicious daemon Workflows go · github.com/argoproj/argo-workflows/v3 2024-10-28 medium4.7 CVE-2024-41666 The Argo CD web terminal session does not handle the revocation of user permissions properly go · github.com/argoproj/argo-cd/v2 2024-07-24 high7.5 CVE-2024-40634 Argo CD Unauthenticated Denial of Service (DoS) Vulnerability via /api/webhook Endpoint go · github.com/argoproj/argo-cd, go · github.com/argoproj/argo-cd/v2 2024-07-22 medium5.3 CVE-2024-37152 Unauthenticated Access to sensitive settings in Argo CD go · github.com/argoproj/argo-cd/v2/server 2024-06-06 medium4.3 CVE-2024-36106 Argo-cd authenticated users can enumerate clusters by name go · github.com/argoproj/argo-cd 2024-06-06 critical9.0 CVE-2024-31989 ArgoCD Vulnerable to Use of Risky or Missing Cryptographic Algorithms in Redis Cache go · github.com/argoproj/argo-cd/v2, go · github.com/argoproj/argo-cd 2024-05-21 medium6.5 CVE-2024-32476 Argo CD vulnerable to a Denial of Service via malicious jqPathExpressions in ignoreDifferences go · github.com/argoproj/argo-cd/v2 2024-04-26 medium4.8 CVE-2024-31990 Argo CD's API server does not enforce project sourceNamespaces go · github.com/argoproj/argo-cd/v2 2024-04-15 medium6.5 CVE-2024-29893 ArgoCD's repo server has Uncontrolled Resource Consumption vulnerability go · github.com/argoproj/argo-cd/v2 2024-03-29 high7.5 CVE-2024-21662 Bypassing Rate Limit and Brute Force Protection Using Cache Overflow go · github.com/argoproj/argo-cd/v2 2024-03-18 high7.5 CVE-2024-21661 Denial of Service (DoS) Vulnerability Due to Unsafe Array Modification in Multi-threaded Environment go · github.com/argoproj/argo-cd, go · github.com/argoproj/argo-cd/v2 2024-03-18 critical9.8 CVE-2024-21652 Bypassing Brute Force Protection via Application Crash and In-Memory Data Loss go · github.com/argoproj/argo-cd/v2 2024-03-18 critical9.0 CVE-2024-28175 Cross-site scripting on application summary component go · github.com/argoproj/argo-cd/v2, go · github.com/argoproj/argo-cd 2024-03-13 medium6.4 CVE-2023-50726 Users with `create` but not `override` privileges can perform local sync go · github.com/argoproj/argo-cd, go · github.com/argoproj/argo-cd/v2 2024-03-13 high8.3 CVE-2024-22424 github.com/argoproj/argo-cd Cross-Site Request Forgery vulnerability go · github.com/argoproj/argo-cd, go · github.com/argoproj/argo-cd/v2 2024-01-19 medium5.0 CVE-2023-40026 Path traversal allows leaking out-of-bound Helm charts from Argo CD repo-server go · github.com/argoproj/argo-cd, go · github.com/argoproj/argo-cd/v2 2023-09-27 medium6.5 CVE-2023-40584 Argo CD repo-server Denial of Service vulnerability go · github.com/argoproj/argo-cd/v2 2023-09-07 critical9.9 CVE-2023-40029 Argo CD cluster secret might leak in cluster details page go · github.com/argoproj/argo-cd/v2 2023-09-07 high7.1 CVE-2023-40025 Argo CD web terminal session doesn't expire go · github.com/argoproj/argo-cd/v2 2023-08-23 medium5.3 CVE-2022-41354 Argo CD authenticated but unauthorized users may enumerate Application names via the API go · github.com/argoproj/argo-cd, go · github.com/argoproj/argo-cd/v2 2023-03-23 critical9.1 CVE-2023-23947 Users with any cluster secret update access may update out-of-bounds cluster secrets go · github.com/argoproj/argo-cd 2023-02-16 medium6.3 CVE-2023-25163 Argo CD leaks repository credentials in user-facing error messages and in logs go · github.com/argoproj/argo-cd/v2 2023-02-08 critical9.0 CVE-2023-22482 JWT audience claim is not verified go · github.com/argoproj/argo-cd 2023-01-25 high8.5 CVE-2023-22736 Controller reconciles apps outside configured namespaces when sharding is enabled go · github.com/argoproj/argo-cd/v2 2023-01-25 low2.6 CVE-2022-31102 Argo CD SSO users vulnerable to Cross-site Scripting go · github.com/argoproj/argo-cd 2022-07-12 high8.3 CVE-2022-31105 Argo CD certificate verification is skipped for connections to OIDC providers go · github.com/argoproj/argo-cd 2022-07-12 high8.8 CVE-2022-1025 Argo CD improper access control bug can allow malicious user to escalate privileges to admin level go · github.com/argoproj/argo-cd, go · github.com/argoproj/argo-cd/v2 2022-07-12 medium6.5 CVE-2022-31016 DoS through large manifest files in Argo CD go · github.com/argoproj/argo-cd, go · github.com/argoproj/argo-cd/v2 2022-06-21 medium4.3 CVE-2022-31036 Symlink following allows leaking out-of-bounds YAML files from Argo CD repo-server go · github.com/argoproj/argo-cd, go · github.com/argoproj/argo-cd/v2 2022-06-21 critical9.0 CVE-2022-31035 Argo CD's external URLs for Deployments can include JavaScript go · github.com/argoproj/argo-cd, go · github.com/argoproj/argo-cd/v2 2022-06-21

Get notifications

Subscribe to new vulnerabilities and early warnings from the last seven days. Pick what matters to your stack and copy the address into any feed reader. More filters appear when you pick a type.

Format:
Open feed

Early warnings are advisories that are published before or without a CVE number, for example malicious packages, advisories with a CVE still pending and reports that are not reviewed yet. Confidence says how well an entry is checked: high, medium or low.

About this dashboard

The dashboard keeps its own index of security advisories and refreshes it every 30 minutes. It merges the national vulnerability database, package advisories, malware reports and the catalog of vulnerabilities that are exploited in the wild into one record per issue. Reports about the same flaw are combined, so nothing is listed twice.

Open any entry for the full record: description, severity vector, affected packages and versions, fixed versions, weakness class, exploitation probability and references.

Sources: the GitHub Advisory Database (reviewed advisories, malware reports and unreviewed reports), the National Vulnerability Database, the CVE Program (cve.org) for brand-new records, the OpenSSF malicious packages list, the CISA catalog of Known Exploited Vulnerabilities and Microsoft's blocklist of malicious VS Code extensions. Every entry names its sources on its detail page.

This product uses the NVD API but is not endorsed or certified by the NVD.

Reading the figures

  • Threat level: a rating computed from three numbers shown next to it: critical advisories in the last 24 hours, vulnerabilities newly confirmed as exploited this week and malware reports this week. It is a quick orientation, not an official warning level.
  • Severity: scores from 9.0 are critical, 7.0 to 8.9 high, 4.0 to 6.9 medium and 0.1 to 3.9 low. Severity describes how bad a flaw is in general. It does not know whether the component is reachable in your environment.
  • Known exploited: exploitation has been observed in real attacks. These are the entries to patch first. Entries with a fix deadline show how many days are left.
  • Early warnings: advisories that appear before or without a CVE number, for example malicious packages, reviewed advisories with a CVE still pending and reports that are not reviewed yet.
  • Priority queue: critical and high advisories of the last 7 days and everything newly exploited, ordered by exploitation status, severity and score.

Questions

Where does the data come from?
From public vulnerability databases, package advisories and the catalog of exploited vulnerabilities. NetSight collects them into its own index every 30 minutes and merges duplicates.
How do I check whether I am affected?
Search for your product or package name, open the record and compare your installed version with the affected and fixed versions. A product name alone does not mean your version is affected.
What does known exploited mean?
Exploitation of this vulnerability has been observed in real attacks. Such entries carry a date they were confirmed and, where one exists, a deadline for applying the fix.
What is an early warning?
An advisory that is published before or without a CVE number, such as a malicious package or a reviewed advisory whose CVE is still pending. They give you a head start, but the details can change.
Is a high severity always more urgent than a low one?
No. Severity measures technical impact in general. Exposure of the affected system, observed exploitation and the exploitation probability matter as much.
Can I follow new advisories automatically?
Yes. Use the notification builder further down to create an RSS, Atom or JSON feed filtered by severity, technology, ecosystem or exploitation status.