NetSight

Security Dashboard

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

Reset
102 matching advisories · page 3 of 4Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
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 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 medium6.5 CVE-2022-40716 HashiCorp Consul vulnerable to authorization bypass go · github.com/hashicorp/consul 2022-09-23 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 medium5.3 CVE-2022-30689 HashiCorp Vault improper configuration of multi factor authentication go · github.com/hashicorp/vault 2022-05-17 medium5.5 CVE-2022-29810 Insertion of Sensitive Information into Log File in Hashicorp go-getter go · github.com/hashicorp/go-getter 2022-04-27 medium6.5 CVE-2022-25244 Vault Enterprise clusters using the tokenization transform feature can expose the tokenization key through the tokenization key configuration endpoint to autho… hashicorp · vault 2022-03-10 medium6.5 CVE-2022-25243 "Vault and Vault Enterprise 1.8.0 through 1.8.8, and 1.9.3 allowed the PKI secrets engine under certain configurations to issue wildcard certificates to author… hashicorp · vault 2022-03-10 medium6.5 CVE-2022-24687 HashiCorp Consul Ingress Gateway Panic Can Shutdown Servers go · github.com/hashicorp/consul 2022-02-24 medium5.3 CVE-2022-25197 Agent-to-controller security bypass in Jenkins HashiCorp Vault Plugin allows reading arbitrary files maven · com.datapipe.jenkins.plugins:hashicorp-vault-plugin 2022-02-15 medium6.5 CVE-2022-25186 Agent-to-controller security bypass in Jenkins HashiCorp Vault Plugin maven · com.datapipe.jenkins.plugins:hashicorp-vault-plugin 2022-02-15 medium6.5 CVE-2022-24684 Nomad Spread Job Stanza May Trigger Panic in Servers go · github.com/hashicorp/nomad 2022-02-15 medium5.3 CVE-2019-14802 Hashicorp Nomad Information Exposure Through Environmental Variables go · github.com/hashicorp/nomad 2022-02-15 medium5.9 CVE-2022-24686 HashiCorp Nomad Artifact Download Race Condition go · github.com/hashicorp/nomad 2022-02-14 medium6.5 CVE-2022-23109 Improper credentials masking in Jenkins HashiCorp Vault Plugin maven · com.datapipe.jenkins.plugins:hashicorp-vault-plugin 2022-01-12 medium4.9 CVE-2021-45042 In HashiCorp Vault and Vault Enterprise before 1.7.7, 1.8.x before 1.8.6, and 1.9.x before 1.9.1, clusters using the Integrated Storage backend allowed an auth… hashicorp · vault 2021-12-17 medium6.5 CVE-2021-41865 HashiCorp Nomad and Nomad Enterprise 1.1.1 through 1.1.5 allowed authenticated users with job submission capabilities to cause denial of service by submitting … hashicorp · nomad 2021-10-07 medium6.5 CVE-2021-38698 HashiCorp Consul and Consul Enterprise 1.10.1 Txn.Apply endpoint allowed services to register proxies for other services, enabling access to service traffic. go · github.com/hashicorp/consul 2021-09-07 medium5.3 CVE-2021-27668 HashiCorp Vault Enterprise 0.9.2 through 1.6.2 allowed the read of license metadata from DR secondaries without authentication. hashicorp · vault 2021-08-31 medium5.3 CVE-2021-38554 Improper Removal of Sensitive Information Before Storage or Transfer in HashiCorp Vault go · github.com/hashicorp/vault 2021-08-13 medium6.5 CVE-2021-32575 Improper network isolation in Hashicorp Nomad go · github.com/hashicorp/nomad 2021-06-17 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 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

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.