NetSight

Security Dashboard

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

Reset
244 matching advisories · page 8 of 9Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.3 CVE-2020-15511 HashiCorp Terraform Enterprise up to v202006-1 contained a default signup page that allowed user registration even when disabled, bypassing SAML enforcement. hashicorp · terraform_enterprise 2020-07-30 high7.5 CVE-2020-13250 Allocation of Resources Without Limits or Throttling in Hashicorp Consul go · github.com/hashicorp/consul 2020-06-11 high7.5 CVE-2020-13170 Improper Input Validation in HashiCorp Consul go · github.com/hashicorp/consul 2020-06-11 medium5.3 CVE-2020-12797 Incorrect Permission Assignment for Critical Resource in Hashicorp Consul go · github.com/hashicorp/consul 2020-06-11 high7.5 CVE-2020-12758 Denial of Service (DoS) in HashiCorp Consul go · github.com/hashicorp/consul 2020-06-11 high7.5 CVE-2020-13223 Information Disclosure in HashiCorp Vault go · github.com/hashicorp/vault 2020-06-10 critical9.8 CVE-2020-12757 Improper Input Validation in HashiCorp Vault go · github.com/hashicorp/vault-plugin-secrets-gcp 2020-06-10 medium5.4 CVE-2020-10944 HashiCorp Nomad and Nomad Enterprise up to 0.10.4 contained a cross-site scripting vulnerability such that files from a malicious workload could cause arbitrar… hashicorp · nomad 2020-04-28 critical9.1 CVE-2020-10661 HashiCorp Vault Improper Privilege Management go · github.com/hashicorp/vault 2020-03-23 medium5.3 CVE-2020-10660 HashiCorp Vault Improper Privilege Management go · github.com/hashicorp/vault 2020-03-23 high7.5 CVE-2019-19879 HashiCorp Sentinel up to 0.10.1 incorrectly parsed negation in certain policy expressions. hashicorp · sentinel 2020-02-14 critical9.8 CVE-2020-7956 Improper Certificate Validation in HashiCorp Nomad go · github.com/hashicorp/nomad 2020-01-31 medium5.3 CVE-2020-7955 Incorrect Authorization in HashiCorp Consul go · github.com/hashicorp/consul 2020-01-31 high7.5 CVE-2020-7219 Denial of Service (DoS) in HashiCorp Consul go · github.com/hashicorp/consul 2020-01-31 high7.5 CVE-2020-7218 Allocation of Resources Without Limits or Throttling in HashiCorp Nomad go · github.com/hashicorp/nomad 2020-01-31 high7.5 CVE-2020-7220 Improper Resource Shutdown or Release in HashiCorp Vault go · github.com/hashicorp/vault 2020-01-23 high7.5 CVE-2019-19316 Use of a Broken or Risky Cryptographic Algorithm in Terraform go · github.com/hashicorp/terraform 2019-12-02 critical9.8 CVE-2019-12618 Hashicorp Nomad Access Control Issues go · github.com/hashicorp/nomad 2019-08-12 high7.5 CVE-2019-12291 HashiCorp Consul Incorrect Access Control vulnerability go · github.com/hashicorp/consul 2019-06-06 high7.4 CVE-2019-9764 HashiCorp Consul vulnerable to Origin Validation Error go · github.com/hashicorp/consul 2019-03-26 high8.1 CVE-2019-8336 HashiCorp Consul Access Restriction Bypass go · github.com/hashicorp/consul 2019-03-05 medium5.9 CVE-2018-19653 HashiCorp Consul can use cleartext agent-to-agent RPC communication go · github.com/hashicorp/consul 2018-12-09 high8.1 CVE-2018-19786 HashiCorp Vault before 1.0.0 writes the master key to the server log in certain unusual or misconfigured scenarios in which incorrect data comes from the autos… hashicorp · vault 2018-12-05 medium5.3 CVE-2018-15869 An Amazon Web Services (AWS) developer who does not specify the --owners flag when describing images via AWS CLI, and therefore not properly validating source … hashicorp · packer 2018-08-25 high7.8 CVE-2017-16873 It is possible to exploit an unsanitized PATH in the suid binary that ships with vagrant-vmware-fusion 4.0.25 through 5.0.4 in order to escalate to root privil… hashicorp · vagrant_vmware_fusion 2018-03-29 high7.0 CVE-2017-16839 Hashicorp vagrant-vmware-fusion 5.0.4 allows local users to steal root privileges if VMware Fusion is not installed. hashicorp · vagrant_vmware_fusion 2018-03-29 high7.8 CVE-2017-16512 The vagrant update process in Hashicorp vagrant-vmware-fusion 5.0.2 through 5.0.4 allows local users to steal root privileges via a crafted update request when… hashicorp · vagrant_vmware_fusion 2018-03-29 critical9.8 CVE-2018-9057 aws/resource_aws_iam_user_login_profile.go in the HashiCorp Terraform Amazon Web Services (AWS) provider through v1.12.0 has an inappropriate PRNG algorithm an… go · github.com/hashicorp/terraform-provider-aws 2018-03-27 high7.8 CVE-2017-16777 If HashiCorp Vagrant VMware Fusion plugin (aka vagrant-vmware-fusion) 5.0.3 is installed but VMware Fusion is not, a local attacker can create a fake applicati… hashicorp · vagrant 2017-11-16 high7.8 CVE-2017-16001 In HashiCorp Vagrant VMware Fusion plugin (aka vagrant-vmware-fusion) 5.0.1, a local attacker or malware can silently subvert the plugin update process in orde… hashicorp · vagrant 2017-11-06

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.