NetSight

Security Dashboard

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

Reset
244 matching advisories · page 7 of 9Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2021-36213 HashiCorp Consul L7 deny intention results in an allow action go · github.com/hashicorp/consul 2021-07-17 high7.5 CVE-2021-32574 Hashicorp Consul Missing SSL Certificate Validation go · github.com/hashicorp/consul 2021-07-17 medium6.5 CVE-2021-32575 Improper network isolation in Hashicorp Nomad go · github.com/hashicorp/nomad 2021-06-17 high7.4 CVE-2021-32923 Invalid session token expiration go · github.com/hashicorp/vault 2021-06-03 high7.5 CVE-2021-32074 Vault GitHub Action did not correctly mask multi-line secrets in output actions · hashicorp/vault-action 2021-05-07 critical9.8 CVE-2021-30476 HashiCorp Terraform’s Vault Provider (terraform-provider-vault) did not correctly configure GCE-type bound labels for Vault’s GCP auth method. hashicorp · terraform_provider 2021-04-22 high7.5 CVE-2021-29653 HashiCorp Vault and Vault Enterprise 1.5.1 and newer, under certain circumstances, may exclude revoked but unexpired certificates from the CRL. hashicorp · vault 2021-04-22 high7.5 CVE-2021-27400 HashiCorp Vault and Vault Enterprise Cassandra integrations (storage backend and database secrets engine plugin) did not validate TLS certificates when connect… hashicorp · vault 2021-04-22 high7.5 CVE-2021-28156 HashiCorp Consul Enterprise version 1.8.0 up to 1.9.4 audit log can be bypassed by specifically crafted HTTP events. hashicorp · consul 2021-04-20 medium6.1 CVE-2020-25864 HashiCorp Consul Cross-site Scripting vulnerability go · github.com/hashicorp/consul 2021-04-20 medium6.5 CVE-2021-3153 HashiCorp Terraform Enterprise up to v202102-2 failed to enforce an organization-level setting that required users within an organization to have two-factor au… hashicorp · terraform_enterprise 2021-03-26 high7.5 CVE-2021-3283 Improper Privilege Management in HashiCorp Nomad go · github.com/hashicorp/nomad 2021-02-01 high7.5 CVE-2021-3282 Improper Authentication in HashiCorp Vault go · github.com/hashicorp/vault 2021-02-01 medium5.3 CVE-2021-3024 HashiCorp Vault and Vault Enterprise disclosed the internal IP address of the Vault node when responding to some invalid, unauthenticated HTTP requests. hashicorp · vault 2021-02-01 medium5.3 CVE-2020-25594 HashiCorp Vault and Vault Enterprise allowed for enumeration of Secrets Engine mount paths via unauthenticated HTTP requests. hashicorp · vault 2021-02-01 medium4.9 CVE-2020-8567 Kubernetes Secrets Store CSI Driver plugins arbitrary file write go · github.com/hashicorp/vault-csi-provider, go · github.com/Azure/secrets-store-csi-driver-provider-azure, go · github.com/GoogleCloudPlatform/secrets-store-csi-driver-provider-gcp 2021-01-21 high8.6 CVE-2021-3121 Improper Input Validation in GoGo Protobuf go · github.com/gogo/protobuf 2021-01-11 medium5.3 CVE-2020-35453 HashiCorp Vault Enterprise’s Sentinel EGP policy feature incorrectly allowed requests to be processed in parent and sibling namespaces. hashicorp · vault 2020-12-17 medium5.4 CVE-2020-35177 Enumeration of users in HashiCorp Vault go · github.com/hashicorp/vault 2020-12-17 critical9.8 CVE-2020-35192 The official vault docker images before 0.11.6 contain a blank password for a root user. hashicorp · vault 2020-12-17 critical9.8 CVE-2020-29564 The official Consul Docker images 0.7.1 through 1.4.2 contain a blank password for a root user. hashicorp · consul_docker_image 2020-12-08 high7.5 CVE-2020-29529 Unsafe tar unpacking in HashiCorp go-slug go · github.com/hashicorp/go-slug 2020-12-03 medium6.5 CVE-2020-28348 Path Traversal in HashiCorp Nomad go · github.com/hashicorp/nomad 2020-11-24 medium6.5 CVE-2020-28053 Privilege Escalation in HashiCorp Consul go · github.com/hashicorp/consul 2020-11-23 high7.5 CVE-2020-25201 Denial of service in HashiCorp Consul go · github.com/hashicorp/consul 2020-11-04 critical9.1 CVE-2020-27195 Use After Free in HashiCorp Nomad go · github.com/hashicorp/nomad 2020-10-22 critical9.8 CVE-2020-25816 Token leases could outlive their TTL in HashiCorp Vault go · github.com/hashicorp/vault 2020-09-30 high8.2 CVE-2020-16251 HashiCorp Vault Authentication bypass go · github.com/hashicorp/vault 2020-08-26 high8.2 CVE-2020-16250 Authentication Bypass by Spoofing and Insufficient Verification of Data Authenticity in Hashicorp Vault go · github.com/hashicorp/vault 2020-08-26 high7.5 CVE-2020-24359 Improper Input Validation in vault-ssh-helper go · github.com/hashicorp/vault-ssh-helper 2020-08-20

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.