NetSight

Security Dashboard

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

Reset
244 matching advisories · page 5 of 9Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium4.7 CVE-2023-25000 HashiCorp Vault's implementation of Shamir's secret sharing vulnerable to cache-timing attacks go · github.com/hashicorp/vault 2023-03-30 medium6.5 CVE-2023-0665 HashiCorp Vault's PKI mount vulnerable to denial of service go · github.com/hashicorp/vault 2023-03-30 medium6.7 CVE-2023-0620 HashiCorp Vault’s Microsoft SQL Database Storage Backend Vulnerable to SQL Injection Via Configuration File go · github.com/hashicorp/vault 2023-03-30 high8.8 CVE-2023-1299 Nomad Job Submitter Privilege Escalation Using Workload Identity go · github.com/hashicorp/nomad 2023-03-14 medium5.3 CVE-2023-1296 Hashicorp Nomad ACLs Cannot Deny Access to Workload’s Own Variables go · github.com/hashicorp/nomad 2023-03-14 high8.1 CVE-2023-24999 Hashicorp Vault Fails to Verify if Approle SecretID Belongs to Role During a Destroy Operation go · github.com/hashicorp/vault 2023-03-11 medium6.5 CVE-2023-0845 Consul Server Panic when Ingress and API Gateways Configured with Peering Connections go · github.com/hashicorp/consul 2023-03-09 medium6.5 CVE-2023-0821 Uncontrolled Resource Consumption in Hashicorp Nomad go · github.com/hashicorp/nomad 2023-02-16 medium4.2 CVE-2023-0475 Data Amplification in HashiCorp go-getter go · github.com/hashicorp/go-getter, go · github.com/hashicorp/go-getter/v2 2023-02-16 high7.1 CVE-2023-0690 HashiCorp Boundary Workers Store Rotated Credentials in Plaintext Even When Key Management Service Configured go · github.com/hashicorp/boundary 2023-02-08 high7.5 CVE-2022-3920 Missing Authorization in HashiCorp Consul go · github.com/hashicorp/consul 2022-11-16 low2.7 CVE-2022-3867 HashiCorp Nomad vulnerable to Insufficient Session Expiration go · github.com/hashicorp/nomad 2022-11-10 medium5.0 CVE-2022-3866 HashiCorp Nomad vulnerable to non-sensitive metadata exposure go · github.com/hashicorp/nomad 2022-11-10 medium6.1 CVE-2022-36182 Hashicorp Boundary vulnerable to clickjacking go · github.com/hashicorp/boundary 2022-10-27 medium5.3 CVE-2022-41316 HashiCorp Vault's revocation list not respected go · github.com/hashicorp/vault 2022-10-12 medium6.5 CVE-2022-41606 Nomad Panics On Job Submission With Bad Artifact Stanza Source URL go · github.com/hashicorp/nomad 2022-10-12 high7.8 CVE-2022-42717 An issue was discovered in Hashicorp Packer before 2.3.1. hashicorp · vagrant 2022-10-11 medium6.5 CVE-2022-40716 HashiCorp Consul vulnerable to authorization bypass go · github.com/hashicorp/consul 2022-09-23 high7.1 CVE-2021-41803 HashiCorp Consul does not properly validate node or segment names prior to usage in JWT claim assertions go · github.com/hashicorp/consul 2022-09-23 critical9.1 CVE-2022-40186 HashiCorp Vault vulnerable to incorrect metadata access go · github.com/hashicorp/vault 2022-09-22 critical9.9 CVE-2022-36130 HashiCorp Boundary up to 0.10.1 did not properly perform data integrity checks to ensure the resources were associated with the correct scopes, allowing potent… hashicorp · boundary 2022-09-01 high7.5 CVE-2022-38149 HashiCorp Consul Template could reveal Vault secret contents in error messages go · github.com/hashicorp/consul-template 2022-08-17 medium4.2 CVE-2022-36888 Jenkins HashiCorp Vault Plugin does not perform permission checks in several HTTP endpoints that perform Vault connection tests maven · com.datapipe.jenkins.plugins:hashicorp-vault-plugin 2022-07-27 critical9.1 CVE-2022-36129 HashiCorp Vault Enterprise 1.7.0 through 1.9.7, 1.10.4, and 1.11.0 clusters using Integrated Storage expose an unauthenticated API endpoint that could be abuse… hashicorp · vault 2022-07-26 critical9.8 CVE-2022-30324 Privilege escalation in Hashicorp Nomad go · github.com/hashicorp/nomad 2022-06-02 high8.6 CVE-2022-30323 HashiCorp go-getter unsafe downloads could lead to asymmetric resource exhaustion go · github.com/hashicorp/go-getter, go · github.com/hashicorp/go-getter/v2, go · github.com/hashicorp/go-getter/s3/v2 +1 2022-05-25 high8.6 CVE-2022-30322 HashiCorp go-getter unsafe downloads could lead to arbitrary host access go · github.com/hashicorp/go-getter, go · github.com/hashicorp/go-getter/v2, go · github.com/hashicorp/go-getter/s3/v2 +1 2022-05-25 high8.6 CVE-2022-30321 HashiCorp go-getter unsafe downloads go · github.com/hashicorp/go-getter, go · github.com/hashicorp/go-getter/v2, go · github.com/hashicorp/go-getter/s3/v2 +1 2022-05-25 critical9.8 CVE-2022-26945 HashiCorp go-getter command injection go · github.com/hashicorp/go-getter, go · github.com/hashicorp/go-getter/v2, go · github.com/hashicorp/go-getter/s3/v2 +1 2022-05-25 medium5.3 CVE-2022-30689 HashiCorp Vault improper configuration of multi factor authentication go · github.com/hashicorp/vault 2022-05-17

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.